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.
CVE-2026-56725
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd 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).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7HIGHmedium confidence
- EG Risk
- 54EG Risk 54/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 computedSeverity87% × 45%Exploitation0% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: A fix is available. 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
- 33rd
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. 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). 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, 2026commit a04a95b69496 (zammad/zammad)
Fix landed in zammad/zammad commit a04a95b69496 — awaiting tagged release
https://github.com/zammad/zammad/commit/a04a95b69496306af4c1fbd369a54981122e67c0Denial of Service via OTRS Import Controller · Advisory · zammad/zammad · GitHub
https://github.com/zammad/zammad/security/advisories/GHSA-45cx-9mrq-mmcjWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 22× 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 03:09 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 01:35 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 00:03 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 22:04 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 20:31 UTCEG score recompute
- 2026-09-29 19:44 UTCEG score recompute
- 2026-09-29 16:46 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-29 03:39 UTCEG score recompute
- 2026-09-28 14:51 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 21:51 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 20:15 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 18:38 UTCEG score recompute
- 2026-09-25 17:19 UTCEG score recompute
- 2026-09-25 17:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-56725?
When was CVE-2026-56725 disclosed?
Is CVE-2026-56725 actively exploited?
What is the CVSS score of CVE-2026-56725?
How do I remediate CVE-2026-56725?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56725
Is Your Infrastructure Affected by CVE-2026-56725?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.