# CVE-2026-34718: Zammad improperly neutralizes of script-related HTML tags in ticket articles

> Attackers can store malicious data URIs in ticket articles, though CSP prevents execution, requiring an upgrade to Zammad to fully sanitize content.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-c2cf-9fc7-jhf3

## What is CVE-2026-34718?

CVE-2026-34718 is a medium-severity cross-site scripting vulnerability in Zammad Zammad, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.1 and 6.5.4, the HTML sanitizer for ticket articles was missing proper sanitization of data: ... URI schemes, resulting in storing such malicious content in the database of the Zammad instance. The Zammad GUI is rendering this content, due to applied CSP rules no harm was done by e.g., clicking such a link. This vulnerability is fixed in 7.0.1 and 6.5.4.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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

It affects 1 product.


Products: Zammad Zammad.

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

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

## Is CVE-2026-34718 being exploited?

There is no known exploitation of CVE-2026-34718 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-34718 and fix it if it is affected.

What it is: CVE-2026-34718 is a medium-severity cross-site scripting vulnerability in Zammad Zammad, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-34718 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-34718/ (Markdown: https://insights.sbomify.com/CVE-2026-34718/index.md)
```

## Sources

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

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