CVE-2026-67227: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1, Atom exhaustion: toatom on global-parameter :name. resourceexists/2 (and the PUT/DELETE handlers) call rabbitdatacoercion:toatom/1 on the :name URL path segment. toatom/1 uses binarytoatom/2 (unsafe). The endpoint requires policymaker (not management, but below A user with the policymaker tag can crash the node by exhausting the atom table via repeated requests to /api/global-parameters/:name with unique :name Management plugin enabled policymaker tag ~1M HTTP. This issue is fixed in versions 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1.
AI Analysis
Technical Summary
RabbitMQ versions 4.0.0 through versions prior to 4.0.22, 4.1.14, 4.2.7, and 4.3.1 contain a vulnerability where the atom table can be exhausted due to unsafe use of binary_to_atom conversion in the handling of the :name URL path segment in the /api/global-parameters/:name endpoint. This endpoint requires the policymaker tag, which is a privilege below management. An attacker with policymaker privileges can cause a denial of service by crashing the node through repeated requests with unique :name values, leading to uncontrolled resource consumption (CWE-400).
Potential Impact
An attacker with policymaker privileges on a RabbitMQ server can cause a denial of service by exhausting the atom table, crashing the node. This affects the availability of the messaging service. The vulnerability does not allow privilege escalation or code execution but impacts service stability.
Mitigation Recommendations
This vulnerability is fixed in RabbitMQ versions 4.0.22, 4.1.14, 4.2.7, and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No other mitigation or workaround is indicated in the advisory.
CVE-2026-67227: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1, Atom exhaustion: toatom on global-parameter :name. resourceexists/2 (and the PUT/DELETE handlers) call rabbitdatacoercion:toatom/1 on the :name URL path segment. toatom/1 uses binarytoatom/2 (unsafe). The endpoint requires policymaker (not management, but below A user with the policymaker tag can crash the node by exhausting the atom table via repeated requests to /api/global-parameters/:name with unique :name Management plugin enabled policymaker tag ~1M HTTP. This issue is fixed in versions 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1.
CVSS v4.0
Score 5.9medium
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ versions 4.0.0 through versions prior to 4.0.22, 4.1.14, 4.2.7, and 4.3.1 contain a vulnerability where the atom table can be exhausted due to unsafe use of binary_to_atom conversion in the handling of the :name URL path segment in the /api/global-parameters/:name endpoint. This endpoint requires the policymaker tag, which is a privilege below management. An attacker with policymaker privileges can cause a denial of service by crashing the node through repeated requests with unique :name values, leading to uncontrolled resource consumption (CWE-400).
Potential Impact
An attacker with policymaker privileges on a RabbitMQ server can cause a denial of service by exhausting the atom table, crashing the node. This affects the availability of the messaging service. The vulnerability does not allow privilege escalation or code execution but impacts service stability.
Mitigation Recommendations
This vulnerability is fixed in RabbitMQ versions 4.0.22, 4.1.14, 4.2.7, and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No other mitigation or workaround is indicated in the advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-28T19:50:39.437Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab6a5d5f7a7c5410605563f
Added to database: 09/25/2026, 16:48:21 UTC
Last enriched: 09/25/2026, 17:03:38 UTC
Last updated: 09/26/2026, 04:07:33 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.