CVE-2026-67222: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, mechanisms/1 applied list_to_atom/1 to every colon-delimited token in an attacker-controlled auth_mechanism value, permanently consuming Erlang VM atoms and allowing the node to be crashed with a large request. Exploitation requires the Shovel or Federation plugin to be in use, and setting auth_mechanism requires the policymaker tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
AI Analysis
Technical Summary
RabbitMQ versions 3.13.0 through 3.13.14, 4.0.0 through 4.0.19, 4.1.0 through 4.1.10, and 4.2.0 through 4.2.5 contain a vulnerability (CWE-400) where the function list_to_atom/1 is applied to every colon-delimited token in an attacker-controlled auth_mechanism value. This leads to permanent consumption of Erlang VM atoms, which are a limited resource, potentially causing the RabbitMQ node to crash when a large request is made. Exploitation requires the Shovel or Federation plugin to be enabled and the attacker to have the policymaker tag to set auth_mechanism. The vulnerability is addressed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
Successful exploitation results in uncontrolled resource consumption of Erlang VM atoms, leading to a denial of service by crashing the RabbitMQ node. The impact is limited to nodes with the Shovel or Federation plugin enabled and where the attacker has the policymaker tag to set auth_mechanism. There is no indication of privilege escalation or data disclosure.
Mitigation Recommendations
Upgrade to RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later where this issue is fixed. If upgrading immediately is not possible, restrict access to the policymaker tag and disable the Shovel or Federation plugins if they are not required to reduce exposure. Monitor vendor advisories for any additional guidance.
CVE-2026-67222: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, mechanisms/1 applied list_to_atom/1 to every colon-delimited token in an attacker-controlled auth_mechanism value, permanently consuming Erlang VM atoms and allowing the node to be crashed with a large request. Exploitation requires the Shovel or Federation plugin to be in use, and setting auth_mechanism requires the policymaker tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
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 3.13.0 through 3.13.14, 4.0.0 through 4.0.19, 4.1.0 through 4.1.10, and 4.2.0 through 4.2.5 contain a vulnerability (CWE-400) where the function list_to_atom/1 is applied to every colon-delimited token in an attacker-controlled auth_mechanism value. This leads to permanent consumption of Erlang VM atoms, which are a limited resource, potentially causing the RabbitMQ node to crash when a large request is made. Exploitation requires the Shovel or Federation plugin to be enabled and the attacker to have the policymaker tag to set auth_mechanism. The vulnerability is addressed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
Successful exploitation results in uncontrolled resource consumption of Erlang VM atoms, leading to a denial of service by crashing the RabbitMQ node. The impact is limited to nodes with the Shovel or Federation plugin enabled and where the attacker has the policymaker tag to set auth_mechanism. There is no indication of privilege escalation or data disclosure.
Mitigation Recommendations
Upgrade to RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later where this issue is fixed. If upgrading immediately is not possible, restrict access to the policymaker tag and disable the Shovel or Federation plugins if they are not required to reduce exposure. Monitor vendor advisories for any additional guidance.
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: 6ab6a25af7a7c54106018e26
Added to database: 09/25/2026, 16:33:30 UTC
Last enriched: 09/25/2026, 16:48:57 UTC
Last updated: 09/26/2026, 03:44:27 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.