Quick answers
- Is CVE-2026-56733 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56733 being exploited in the wild.
- How severe is CVE-2026-56733?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- Zammad before 7.0.2 and 7.1.0.
- Is there a fix for CVE-2026-56733?
- A patch was published on 2026: Fixed in versions 7.0.2 and 7.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56733 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-56733?
- 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 stems from improper validation in the authorization cascade during identity object initialization, where granular token-based restrictions are bypassed by the parent account's authorization context. An attacker with a restricted API token can exploit this logic flaw to escalate privileges and create unrestricted administrator accounts, gaining full system access without proper permission validation.
Affected products
- Zammad Zammad before 7.0.2 and 7.1.0
Timeline
- 2026-09-25: disclosed
- 2026: patched: Fixed in versions 7.0.2 and 7.1.0