CVE-2026-67228: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
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.
AI Analysis
Technical Summary
RabbitMQ versions before 4.2.7 and 4.3.1 have a vulnerability in the runtime-parameters lookup path where the :component segment of the request URL is coerced into an Erlang atom using rabbit_data_coercion:to_atom/1 without checking if the atom already exists. This allows an authorized policymaker to create many new atoms by supplying distinct component values, exhausting the atom table and crashing the node. The issue is fixed by using a safe helper that only converts to existing atoms, preventing uncontrolled atom creation.
Potential Impact
An attacker with policymaker privileges can cause a denial of service by crashing the RabbitMQ node through exhaustion of the Erlang atom table. This requires approximately one million requests with distinct component values. The vulnerability does not allow privilege escalation or remote code execution but results in service disruption.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 4.2.7 and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation is required if running these fixed versions.
CVE-2026-67228: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
Description
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.
CVSS v4.0
Score 6.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 before 4.2.7 and 4.3.1 have a vulnerability in the runtime-parameters lookup path where the :component segment of the request URL is coerced into an Erlang atom using rabbit_data_coercion:to_atom/1 without checking if the atom already exists. This allows an authorized policymaker to create many new atoms by supplying distinct component values, exhausting the atom table and crashing the node. The issue is fixed by using a safe helper that only converts to existing atoms, preventing uncontrolled atom creation.
Potential Impact
An attacker with policymaker privileges can cause a denial of service by crashing the RabbitMQ node through exhaustion of the Erlang atom table. This requires approximately one million requests with distinct component values. The vulnerability does not allow privilege escalation or remote code execution but results in service disruption.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 4.2.7 and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation is required if running these fixed versions.
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: 6ab43b0df7a7c54106517561
Added to database: 09/23/2026, 20:48:13 UTC
Last enriched: 09/23/2026, 21:02:59 UTC
Last updated: 09/24/2026, 01:57:04 UTC
Views: 9
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.