CVE-2026-63205

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% (22nd 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.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when creating or updating an email signature, Zammad processes inline images referenced in the signature body. If a signature body contains an HTML img tag pointing to any existing attachment, the system copies that attachment into a new signature-owned record, without checking whether the user has permission to access the original attachment. The newly created copy is then downloadable by the same channel-admin user, because attachment access is determined by the copy's owner (the signature), not the original object (e.g., a ticket or knowledge-base article). This allows a user with any of the admin.channel_email, admin.channel_google, admin.channel_microsoft365, or admin.channel_microsoft_graph permissions to read attachments they would otherwise be denied access to, such as ticket attachments belonging to groups they are not a member of. This issue is fixed in version 7.1.2.

CVSS v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
23
EG Risk 23/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 computed
Severity51% × 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.3%
EPSS %ILE
22nd
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 29, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
Patch available. Sources: github_commit, github.
github_commit

commit f3e4da83621e (zammad/zammad)

Fix landed in zammad/zammad commit f3e4da83621e — awaiting tagged release

https://github.com/zammad/zammad/commit/f3e4da83621efad8443a4e9fe6bd87befad47c44
github Patch Available

Channel admins can read unauthorized attachments via signature rich-text body · Advisory · zammad/zammad · GitHub

https://github.com/zammad/zammad/security/advisories/GHSA-pp8r-x7pp-5qj5

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 19× 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.

  1. 2026-10-03 19:42 UTCEG score recompute
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 19:55 UTCEG score recompute
  4. 2026-10-02 17:56 UTCEPSS rescore
  5. 2026-10-01 20:08 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 20:18 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 20:31 UTCEG score recompute
  10. 2026-09-29 19:44 UTCEG score recompute
  11. 2026-09-29 14:38 UTCEG score recompute
  12. 2026-09-28 14:51 UTCEG score recompute
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 19:09 UTCEG score recompute
  15. 2026-09-26 19:22 UTCEG score recompute
  16. 2026-09-26 15:59 UTCEPSS rescore
  17. 2026-09-25 19:34 UTCEG score recompute
  18. 2026-09-25 18:33 UTCEG score recompute
  19. 2026-09-25 18:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63205?
CVE-2026-63205 is a medium vulnerability published on September 25, 2026. Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when creating or updating an email signature, Zammad processes inline images referenced in the signature body. If a signature body contains an HTML img tag pointing to any existing attachment, the system copies that…
When was CVE-2026-63205 disclosed?
CVE-2026-63205 was first published on September 25, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63205 actively exploited?
CVE-2026-63205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63205?
CVE-2026-63205 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-63205?
A fix for CVE-2026-63205 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-63205

Explore →

Is Your Infrastructure Affected by CVE-2026-63205?

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