Is CVE-2026-56732 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56732 being exploited in the wild.

How severe is CVE-2026-56732?

Informational severity, published 25 September 2026.

Is there a fix for CVE-2026-56732?

A patch was published on 2026-06-15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-56732 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-56732?

Check whether you run Zammad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56732: Zammad HTML sanitization session termination

CVE-2026-56732 · Severity: info · Published 2026-09-25

Zammad is an open source helpdesk and customer support system. Prior to version 7.0.2, a flaw in its HTML content filtering allows an attacker to inject crafted HTML elements into support tickets. When another staff member or customer views the malicious ticket, the injected element can trigger their automatic logout, disrupting their work and potentially allowing unauthorized access.

Technologies: Zammad. Vendors: Zammad.

Quick answers

Is CVE-2026-56732 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56732 being exploited in the wild.
How severe is CVE-2026-56732?: Informational severity, published 25 September 2026.
Which products and versions are affected?: Zammad before 7.0.2.
Is there a fix for CVE-2026-56732?: A patch was published on 2026-06-15. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-56732 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-56732?: Check whether you run Zammad at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The HTML sanitizer in Zammad versions before 7.0.2 fails to properly filter specific HTML elements when sanitizing ticket bodies, allowing injection of malicious markup. An authenticated attacker can craft a ticket containing HTML that triggers a logout action when rendered in another user's browser, terminating their session without their action. The fix restricts allowed Zammad API paths in src and srcset attributes to only safe endpoints.

Affected products

Zammad Zammad before 7.0.2

Timeline

2026-09-25: disclosed
2026-06-15: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.