# CVE-2026-34719: Zammad has a Server-side request forgery (SSRF) via webhooks

> Attackers can exploit missing validation in Zammad webhooks to access confidential cloud metadata via server-side request forgery.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:H/SC:L/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-2vgc-vfh2-rw75

## What is CVE-2026-34719?

CVE-2026-34719 is a high-severity server-side request forgery vulnerability in Zammad Zammad, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the webhook model was missing a proper validation for loop back addresses, or link-local addresses — only the URL scheme (HTTP/HTTPS) as well as the hostname was checked. This could end up in retrieving confidential metadata of cloud/hosting providers. The existing check is now extended and is applied when configuring webhooks as well as triggering webhook jobs. This vulnerability is fixed in 7.0.1 and 6.5.4.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-34719?

It affects 1 product.


Products: Zammad Zammad.

## How do I fix CVE-2026-34719?

No fix has been published for CVE-2026-34719 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34719 being exploited?

There is no known exploitation of CVE-2026-34719 in the wild and no public exploit code.

## Other vulnerabilities in Zammad Zammad

- [CVE-2026-102489](https://insights.sbomify.com/CVE-2026-102489/): Zammad GmbH Zammad Session Fixation (high 8.7, exploited in the wild)
- [CVE-2026-102490](https://insights.sbomify.com/CVE-2026-102490/): Zammad GmbH Zammad Improper Privilege Management (high 8.5, exploited in the wild)
- [CVE-2022-48021](https://insights.sbomify.com/CVE-2022-48021/): Code injection in n/a (critical 9.8)
- [CVE-2022-35490](https://insights.sbomify.com/CVE-2022-35490/): Security feature bypass in n/a (critical 9.8)
- [CVE-2021-42090](https://insights.sbomify.com/CVE-2021-42090/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34719 and fix it if it is affected.

What it is: CVE-2026-34719 is a high-severity server-side request forgery vulnerability in Zammad Zammad, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34719 in the wild and no public exploit code.

Affected product: Zammad Zammad. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34719/ (Markdown: https://insights.sbomify.com/CVE-2026-34719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34719
- OSV: https://osv.dev/vulnerability/CVE-2026-34719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34719/
Summaries are generated and may contain mistakes; the official description above is the record.