CVE-2026-67228 json
RabbitMQ: Atom exhaustion: to_atom on runtime-parameter component
published 2026-09-23 46 d ago modified 2026-10-30 9 d ago also BIT-rabbitmq-2026-67228 , EUVD-2026-85653 , GHSA-73qp-fwh4-2q5g
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, The runtime-parameters lookup path coerces the URL :component segment to an atom with rabbit_data_coercion:to_atom/1 in lookup_component/1 (deps/rabbit/src/rabbit_runtime_parameters.erl), creating a new atom for any previously unseen value. A safe helper, rabbit_registry:binary_to_type/1, which uses binary_to_existing_atom with a catch, already exists but is not used at this call site. lookup_component/1 calls rabbit_data_coercion:to_atom(Component) on the :component segment of the request URL, converting an attacker-supplied string into a new atom. Because the Erlang atom table is bounded and atoms are never garbage collected, an authorized policymaker issuing roughly one million requests with distinct component values can exhaust the atom table and crash the node, resulting in a denial of service. Preconditions include Exploitation requires policymaker privileges and roughly one million requests.. This issue is fixed in versions 4.2.7 and 4.3.1.
Patch / fix
- bitnami rabbitmq 4.2.7, 4.3.1
- vmware rabbitmq 4.2.7, 4.3.1
- pivotal_software rabbitmq 4.2.7, 4.3.1
- rabbitmq-server Debian 14 4.3.2-1
debian advisories DEBIAN-CVE-2026-67228
- rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1
red hat advisories RHSA-2026:67552
- rabbitmq-server Azure Linux 3.0 3.13.7-10
azure linux advisories AZL-105777
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
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-67228 updated cvss 4.4
rabbitmq: RabbitMQ: Denial of Service via atom exhaustion in runtime-parameter component
-
Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1affected: no fix planned “Will not fix”
-
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
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 41 d ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/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.7 >=4.3.0, <4.3.1 |
4.2.7 4.3.1 |
Affected products
- rabbitmq rabbitmq-server
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/rabbitmq/rabbitmq-server/security/advisories/GHSA-73qp-fwh4-2q5g
vendor-advisory, web
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.2.7
release-notes, web
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.3.1
release-notes, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-67228
web
Sources
- CVE List CVE-2026-67228
- NVD CVE-2026-67228
- OSV BIT-rabbitmq-2026-67228
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.