CVE-2026-61525

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (27th 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
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: 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. In 7.0.2 and 7.1.0, zammad's session management for websocket and long-polling connections is susceptible to a path traversal attack. Session identifiers supplied by the client are insufficiently validated before being used to construct internal file paths. When the file-based session store is active (the default configuration), an authenticated attacker can manipulate the session identifier to reference locations outside the intended storage directory, leading to the deletion of arbitrary files and directories on the server. Exploitation requires only a low-privilege authenticated session and a single crafted request. Instances configured to use the Redis-based session store are not affected. This issue is fixed in versions 7.0.3 and 7.1.1.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.4% × 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 total (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.4%
EPSS %ILE
27th
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 total (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)3 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 total (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 28, 2026

Advisory Details (3)

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

commit f78ef2434fd8 (zammad/zammad)

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

https://github.com/zammad/zammad/commit/f78ef2434fd8aad6c2fb8a702788f6e3f33565f6
GitHub commit

commit cf3425712e8f (zammad/zammad)

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

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

Arbitrary File Deletion via Unvalidated Session Identifier in Long Polling Controller · Advisory · zammad/zammad · GitHub

https://github.com/zammad/zammad/security/advisories/GHSA-xp9w-hhf3-vfxx

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 41× 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.4% · 27th percentile
  2. 2026-10-13 13:25 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-12 15:50 UTCEG score recompute
  5. 2026-10-11 19:34 UTCEG score recompute
  6. 2026-10-11 16:49 UTCEG score recompute
  7. 2026-10-11 14:11 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-11 03:32 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-10 02:05 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-09 01:02 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-08 00:01 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-06 22:59 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-05 21:58 UTCEG score recompute
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-05 09:28 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-03 19:55 UTCEG score recompute
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-02 18:56 UTCEG score recompute
Show 16 more
  1. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-02 06:26 UTCEG score recompute
  3. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  4. 2026-09-30 16:51 UTCEG score recompute
  5. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  6. 2026-09-29 15:50 UTCEG score recompute
  7. 2026-09-29 03:21 UTCEG score recompute
  8. 2026-09-28 14:51 UTCEG score recompute
  9. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  10. 2026-09-27 20:45 UTCEG score recompute
  11. 2026-09-26 19:44 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  13. 2026-09-25 18:37 UTCEG score recompute
  14. 2026-09-25 17:44 UTCEG score recompute
  15. 2026-09-25 17:19 UTCEG score recomputeFirst assessed: 8.8 HIGH
  16. 2026-09-25 17:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61525?
CVE-2026-61525 is a high-severity vulnerability; its CVE record was published on September 25, 2026. Zammad is a web based open source helpdesk/customer support system. In 7.0.2 and 7.1.0, zammad's session management for websocket and long-polling connections is susceptible to a path traversal attack. Session identifiers supplied by the client are insufficiently validated before being used to…
When was the CVE record for CVE-2026-61525 published?
The CVE record for CVE-2026-61525 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 28, 2026; the record at its source may have been updated since.
Is CVE-2026-61525 actively exploited?
CVE-2026-61525 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61525?
CVE-2026-61525 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61525?
The CVE record for CVE-2026-61525 names the fix: "This issue is fixed in versions 7.0.3 and 7.1.1."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-61525?

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

Book a Demo →Browse All CVEs