Quick answers
- Is CVE-2026-84460 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84460 being exploited in the wild.
- How severe is CVE-2026-84460?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Zammad before 7.1.2.
- Is there a fix for CVE-2026-84460?
- A patch was published on 2026-07-22: Fix committed prior to disclosure Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84460 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84460?
- 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 vulnerability exists in Zammad's REST API tag listing endpoint, which lacked proper permission checks prior to 7.1.2. An authenticated user could call the tag endpoint with an arbitrary ticket ID and retrieve the associated tags regardless of ticket access permissions. The fix adds requires_permission checks ('ticket.agent', 'admin.tag', 'knowledge_base.editor') to the GraphQL tag autocomplete query and REST controller policy, restricting tag visibility to authorized users only.
Affected products
- Zammad Zammad before 7.1.2
Timeline
- 2026-09-25: disclosed
- 2026-07-22: patched: Fix committed prior to disclosure