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.
CVE-2026-56733
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (17th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 39EG Risk 39/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 17th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 25, 2026
Last Modified
September 28, 2026
Advisory Details (3)
Auto-updated Sep 25, 2026commit f059eb2d9835 (zammad/zammad)
Fix landed in zammad/zammad commit f059eb2d9835 — awaiting tagged release
https://github.com/zammad/zammad/commit/f059eb2d9835bdc2666750e805631f67ff485642commit e50ef69beab8 (zammad/zammad)
Fix landed in zammad/zammad commit e50ef69beab8 — awaiting tagged release
https://github.com/zammad/zammad/commit/e50ef69beab897317caa5e9490edba33aa1ac978Incorrect Authorization and Improper Privilege Management in Zammad · Advisory · zammad/zammad · GitHub
https://github.com/zammad/zammad/security/advisories/GHSA-p3mg-2jxr-hww2Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-03 18:26 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 06:02 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 05:23 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 16:17 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 15:30 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-29 03:11 UTCEG score recompute
- 2026-09-28 14:51 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 20:55 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 20:16 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 19:34 UTCEG score recompute
- 2026-09-25 18:38 UTCEG score recompute
- 2026-09-25 17:19 UTCEG score recompute
- 2026-09-25 17:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-56733?
When was CVE-2026-56733 disclosed?
Is CVE-2026-56733 actively exploited?
What is the CVSS score of CVE-2026-56733?
How do I remediate CVE-2026-56733?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56733
Is Your Infrastructure Affected by CVE-2026-56733?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.