Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, when multiple KB categories have different editor roles assigned, a user with knowledge_base.editor in one category can see answer titles and updated_at timestamps from categories they do not have editor access to , via the global quick search. Category names are not leaked, and opening the answer returns "Page not found," but the title alone may disclose sensitive information. This vulnerability is fixed in 7.0.2.
CVE-2026-56729
This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 2.1
- EG Score
- 2.1LOWmedium confidence
- EG Risk
- 10EG Risk 10/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 computedSeverity21% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 29th
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
References (4)
- security-advisories@githubhttps://github.com/zammad/zammad/commit/5076aa1e3081146f826ffaef686c89935fdb4393
- security-advisories@githubhttps://github.com/zammad/zammad/commit/7b6c0adec006e036c9e605c4141a091a6e08aadf
- security-advisories@githubhttps://github.com/zammad/zammad/commit/de5dc4195829e0e1a64307d60c9e06e0e781ab37
- security-advisories@githubhttps://github.com/zammad/zammad/security/advisories/GHSA-4m54-p3mr-22g2
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 15× 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-04 13:07 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 13:57 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-28 14:51 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 18:39 UTCEG score recompute
- 2026-09-25 17:19 UTCEG score recompute
- 2026-09-25 17:04 UTCEG score recompute
- 2026-09-25 17:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-56729?
When was CVE-2026-56729 disclosed?
Is CVE-2026-56729 actively exploited?
What is the CVSS score of CVE-2026-56729?
How do I remediate CVE-2026-56729?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56729
Is Your Infrastructure Affected by CVE-2026-56729?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.