Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, this vulnerability breaks normal ticket isolation boundaries between agents. Any authenticated agent, even one with no active tickets assigned to them, can view the titles, status, labels, and URL links of GitHub/GitLab issues attached to any ticket in the system. This allows an internal user to systematically view GitHub/GitLab issue data linked by other agents or administrators across the organization by simply querying random or sequential ticket IDs. This vulnerability is fixed in 7.0.2.
CVE-2026-56726
MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th 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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.1
- EG Score
- 5.1MEDIUMmedium confidence
- EG Risk
- 28EG Risk 28/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 computedSeverity51% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.3%
- EPSS %ILE
- 25th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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, 2026Patch available. Sources: github, github_commit.
github_commit
commit e50ef69beab8 (zammad/zammad)
Fix landed in zammad/zammad commit e50ef69beab8 — awaiting tagged release
https://github.com/zammad/zammad/commit/e50ef69beab897317caa5e9490edba33aa1ac978github_commit
commit c767f32c006f (zammad/zammad)
Fix landed in zammad/zammad commit c767f32c006f — awaiting tagged release
https://github.com/zammad/zammad/commit/c767f32c006ff9842152f78e12f355f7f485304fgithub Patch Available
Missing authorization check in GitHub + GitLab integration allows cross-ticket data leak · Advisory · zammad/zammad · GitHub
https://github.com/zammad/zammad/security/advisories/GHSA-96hh-fmj3-h4hpWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 18× 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 15:47 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 15:27 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 15:06 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-29 14:58 UTCEG score recompute
- 2026-09-28 14:51 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 20:56 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 20:49 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 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-56726?
CVE-2026-56726 is a medium vulnerability published on September 25, 2026. Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, this vulnerability breaks normal ticket isolation boundaries between agents. Any authenticated agent, even one with no active tickets assigned to them, can view the titles, status, labels, and URL links of…
When was CVE-2026-56726 disclosed?
CVE-2026-56726 was first published on September 25, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56726 actively exploited?
CVE-2026-56726 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56726?
CVE-2026-56726 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56726?
A fix for CVE-2026-56726 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56726
Is Your Infrastructure Affected by CVE-2026-56726?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.