CVE-2026-67415 json
RabbitMQ: Shovel Management Atom Exhaustion Allows Persistent Broker-Wide Denial of Service
published 2026-09-25 44 d ago modified 2026-10-17 22 d ago also BIT-rabbitmq-2026-67415 , EUVD-2026-87225 , GHSA-8mpg-qw9r-m5cr
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, the Shovel parameter parser converted attacker-controlled runtime parameter values into non-garbage-collected Erlang atoms before bounding them or checking a fixed allowlist. Exploitation requires network access to the Management HTTP API, valid credentials with both the management and policymaker tags, permission to set Shovel runtime parameters on a vhost, and the rabbitmq_shovel and rabbitmq_shovel_management plugins to be enabled. The attacker can exhaust the node-wide atom table and deny service, and malicious parameters are stored durably and reparsed when workers start, so atom pressure can recur after restart without a live attacker connection. This issue is fixed in versions 4.2.9 and 4.3.3.
Patch / fix
- bitnami rabbitmq 4.2.9, 4.3.3
- pivotal_software rabbitmq 4.2.9, 4.3.3
- vmware rabbitmq 4.2.9, 4.3.3
- rabbitmq-server Debian 14 4.3.6-1
debian advisories DEBIAN-CVE-2026-67415
- rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1
red hat advisories RHSA-2026:67552
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-67415 updated cvss 4.9
rabbitmq-server: rabbitmq-server: Denial of Service via Shovel plugin atom exhaustion
-
Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1affected: no fix planned “Will not fix”
-
Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-serveraffected: no fix planned “Out of support scope”
-
Red Hat OpenStack Platform 18.0 rabbitmq-serveraffected: no fix available “Fix deferred”
-
Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1fixed: vendor fix RHSA-2026:67552
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 44 d ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-8mpg-qw9r-m5cr referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.9 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 5.9 | CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | rabbitmq | >=4.2.0, <4.2.9 >=4.3.0, <4.3.3 |
4.2.9 4.3.3 |
Affected products
- rabbitmq rabbitmq-server
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/rabbitmq/rabbitmq-server/security/advisories/GHSA-8mpg-qw9r-m5cr
exploit, vendor-advisory, mitigation, advisory
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
release-notes, article
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-67415
web
Sources
- CVE List CVE-2026-67415
- NVD CVE-2026-67415
- OSV BIT-rabbitmq-2026-67415
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.