Quick answers
- Is CVE-2026-102345 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102345 being exploited in the wild.
- How severe is CVE-2026-102345?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Zammad prior to 7.1.2.
- Is there a fix for CVE-2026-102345?
- Yes: fixed in 7.1.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102345 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102345?
- 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.
How to fix
- Fixed in: 7.1.2
Technical details
A stored XSS vulnerability exists in the Vue-based ticket article rendering component (ArticleBubbleBody.vue) where ticket article content is not properly encoded before display. An authenticated user can store malicious markup in a ticket article that executes in the browser context of other users viewing that ticket. The vulnerability requires authentication and user interaction (another user viewing the ticket), and is mitigated by the default CSP; the legacy REST/CoffeeScript interface is unaffected.
Affected products
- Zammad Zammad prior to 7.1.2
Timeline
- 2026-08-04: disclosed
- 2026-08-04: patched: version 7.1.2 released
- 2026-11-04: advisory