Quick answers
- Is CVE-2026-63204 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63204 being exploited in the wild.
- How severe is CVE-2026-63204?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Zammad prior to 7.1.2.
- Is there a fix for CVE-2026-63204?
- A patch was published on 2026-09-25: Version 7.1.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63204 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-63204?
- 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
An authenticated agent with insufficient privilege checks can supply an arbitrary AI analytics run identifier to the ticket summarization endpoint and retrieve the stored provider error message, bypassing authorization controls on which tickets the agent can access. The vulnerability exists in the ticket summarize controller before version 7.1.2 and requires agent-level authentication; only the AI provider error string is exposed, not ticket data itself. The fix improves ticket summarize controller authorization logic to prevent cross-ticket access.
Affected products
- Zammad Zammad prior to 7.1.2
Timeline
- 2026-09-25: disclosed
- 2026-09-25: patched: Version 7.1.2 released