CVE-2026-56733
Zammad: Incorrect Authorization and Improper Privilege Management
- High 8.7
Description
Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2 and 7.1.0, this issue concerns a lack of discursive validation within the authorization cascade. It has been determined that the system-level enforcement of access restrictions during the initialization of new identity objects exhibits a discrepancy: Under specific conditions, the granular restrictions of the access key being used are overridden by the latent authorization authority of the parent account. Consequently, this means that the intended separation of functional areas is nullified, resulting in an uncontrolled expansion of administrative discretion. Due to this potential integrity breach of the entire trust environment, an immediate evaluation of the authorization hierarchies is imperative. Impact An attacker can create new administrator accounts despite token restrictions. This grants full access to all system data (tickets, customers, configuration) and allows the attacker to take complete control of the Zammad instance. Abuse Scenario The vulnerability stems from a lack of synergy between the token-based authorization logic and the target system's functional authorization hierarchy, which allows for iterative escalation of the privileged access context. This issue is fixed in versions 7.0.2 and 7.1.0.
Key facts
- Published
- 25 Sep 2026
- Last changed
- 25 Sep 2026
- Assigned by
- GitHub_M
- EPSS
- 0.267% likely to be exploited in the next 30 days, higher than 19.056% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 8.7CVSS 4.0, Highfrom the CNA (GitHub_M)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| zammad | zammad |
|
Timeline
- 25 Sep 2026 Published
Weakness
References
- https://github.com/zammad/zammad/security/advisories/GHSA-p3mg-2jxr-hww2
- https://github.com/zammad/zammad/commit/e50ef69beab897317caa5e9490edba33aa1ac978
- https://github.com/zammad/zammad/commit/f059eb2d9835bdc2666750e805631f67ff485642
- https://github.com/zammad/zammad/releases/tag/7.0.2
- https://github.com/zammad/zammad/releases/tag/7.1.0