CVE-2026-63006

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, attacker-controlled HTML in inbound emails or tickets could bypass the image URL sanitizer using path traversal sequences. When an authenticated agent views the content, the browser resolves the URL to a protected API endpoint and sends the request with the agent's session cookie, enabling side effects such as forced logout without any user interaction. This issue is fixed in version 7.1.2.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

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 computed (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

September 29, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit 856af85c1241 (zammad/zammad)

Fix landed in zammad/zammad commit 856af85c1241 — awaiting tagged release

https://github.com/zammad/zammad/commit/856af85c12413087d6a74ffee25b16048a5ed8c3
GitHub advisoryMentions a patch (unverified)

HTML sanitizer API path allowlist bypass via interior path traversal in img src/srcset · Advisory · zammad/zammad · GitHub

https://github.com/zammad/zammad/security/advisories/GHSA-33p2-cm7w-62g3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-12 15:49 UTCEG score recompute
  4. 2026-10-11 19:33 UTCEG score recompute
  5. 2026-10-11 16:48 UTCEG score recompute
  6. 2026-10-11 14:10 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-11 02:42 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-10 04:11 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-09 05:38 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-08 07:07 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-07 08:36 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-06 10:05 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-05 11:06 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-10-04 12:35 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-03 14:04 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 15 more
  1. 2026-10-02 15:32 UTCEG score recompute
  2. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-09-30 17:58 UTCEG score recompute
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-09-29 19:22 UTCEG score recompute
  6. 2026-09-29 18:33 UTCEG score recompute
  7. 2026-09-29 13:25 UTCEG score recompute
  8. 2026-09-28 14:51 UTCEG score recompute
  9. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-09-27 16:36 UTCEG score recompute
  11. 2026-09-26 18:05 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-09-25 19:34 UTCEG score recompute
  14. 2026-09-25 18:32 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  15. 2026-09-25 18:30 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63006?
CVE-2026-63006 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, attacker-controlled HTML in inbound emails or tickets could bypass the image URL sanitizer using path traversal sequences. When an authenticated agent views the content, the browser resolves the URL to a protected…
When was the CVE record for CVE-2026-63006 published?
The CVE record for CVE-2026-63006 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-63006 actively exploited?
CVE-2026-63006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63006?
CVE-2026-63006 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63006?
The CVE record for CVE-2026-63006 names the fix: "This issue is fixed in version 7.1.2."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63006

Explore →

Is Your Infrastructure Affected by CVE-2026-63006?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs