CVE-2026-56725

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th 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

Also known asEUVD-2026-87220 (ENISA EUVD)Source: ENISA EUVD

8.7EG
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.7Exploit: 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.0.2, summary An unauthenticated request to POST /api/v1/import/otrs/import_check blocks a Zammad request worker for roughly two minutes. The import_check and import_status actions are missing the setup_done_response guard that other actions in the same controller carry, so they execute on fully set-up production instances. The action enters a retry loop against a blank OTRS endpoint, sleeping for 30 s + 45 s between attempts. Impact An unauthenticated remote attacker denies service to a production Zammad instance. Each request costs almost nothing and forces ~115 seconds of server-side blocking. A few requests per second saturate the Puma worker pool. The condition persists as long as the traffic continues. No account, valid import configuration, or target knowledge beyond the hostname is needed. CSRF token is trivially obtained from any prior GET response. This issue is fixed in version 7.0.2.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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 29, 2026

Advisory Details (2)

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

commit a04a95b69496 (zammad/zammad)

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

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

Denial of Service via OTRS Import Controller · Advisory · zammad/zammad · GitHub

https://github.com/zammad/zammad/security/advisories/GHSA-45cx-9mrq-mmcj

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-56725?
CVE-2026-56725 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. Prior to 7.0.2, summary An unauthenticated request to POST /api/v1/import/otrs/import_check blocks a Zammad request worker for roughly two minutes. The import_check and import_status actions are missing the setup_done_response…
When was the CVE record for CVE-2026-56725 published?
The CVE record for CVE-2026-56725 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-56725 actively exploited?
CVE-2026-56725 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56725?
CVE-2026-56725 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56725?
The CVE record for CVE-2026-56725 names the fix: "This issue is fixed in version 7.0.2."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56725?

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