RabbitMQ is a messaging and streaming broker. From 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service. rabbitMQ 4.3.1 with rabbitmqstreammanagement enabled accepts PUT /api/stream/super-streams/{vhost}/{name} requests from an authenticated management user that can access the target vhost. When the request body contains the binding-keys field, the handler parses the attacker-controlled comma-separated string and builds the full stream-name list before checking whether the user has permission to configure the resulting streams. A low-privileged management user with vhost access but no configure, write, or read permission can therefore force large transient allocations before the resource permission check. In a 768 MB memory-limited container, one HTTP PUT with about 4.5 MB of JSON body killed the RabbitMQ container with Docker state exited true An authenticated low-privileged management user can kill a memory-limited RabbitMQ node with one HTTP This issue is fixed in versions 4.3.3, 4.2.9, and 4.1.11.
CVE-2026-67408
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th 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
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 48EG Risk 48/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 computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 25th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (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 28, 2026
Advisory Details (5)
Auto-updated Sep 25, 2026RabbitMQ 4.3.3
Patch available: rabbitmq/rabbitmq-server v4.3.3
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3RabbitMQ 4.2.9
Patch available: rabbitmq/rabbitmq-server v4.2.9
https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9commit eb11bc44005f (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit eb11bc44005f — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/eb11bc44005fd6d327a78bf171bc598207778c9bcommit 0f3defd176e0 (rabbitmq/rabbitmq-server)
Fix landed in rabbitmq/rabbitmq-server commit 0f3defd176e0 — awaiting tagged release
https://github.com/rabbitmq/rabbitmq-server/commit/0f3defd176e027f54f447beee168d906d4f109b6Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service · Advisory · rabbitmq/rabbitmq-server · GitHub
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2hm4-4438-49q8Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rabbitmq-server4-3-main-4.3.6-1.hum1 | 2026-09-15 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 14× 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 00:56 UTCEG score recompute
- 2026-10-04 00:56 UTCVendor advisory
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 22:56 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-01 20:53 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 18:48 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 16:46 UTCEG score recompute
- 2026-09-29 03:45 UTCEG score recompute
- 2026-09-28 14:44 UTCEG score recompute
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-28 00:44 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 22:42 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 20:39 UTCEG score recompute
- 2026-09-25 19:26 UTCEG score recompute
- 2026-09-25 17:33 UTCEG score recompute
- 2026-09-25 16:39 UTCEG score recompute
- 2026-09-25 16:39 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2026:67552
Frequently asked(5)
What is CVE-2026-67408?
When was CVE-2026-67408 disclosed?
Is CVE-2026-67408 actively exploited?
What is the CVSS score of CVE-2026-67408?
How do I remediate CVE-2026-67408?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-67408
Is Your Infrastructure Affected by CVE-2026-67408?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.