CVE-2026-67220: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
CVE-2026-67220 is a medium severity vulnerability in rabbitmq-server affecting versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6. It involves uncontrolled resource consumption due to atom interning when creating bindings on x-jms-topic exchanges with crafted selector strings. An authenticated low-privilege AMQP user confined to a single vhost can cause a denial of service by crashing the broker node with fewer than 100 bind calls. The issue requires the rabbitmq_jms_topic_exchange plugin to be enabled and specific permissions on exchanges and queues. The vulnerability is fixed in the stated versions.
AI Analysis
Technical Summary
RabbitMQ versions before 3.13.15, 4.0.20, 4.1.11, and 4.2.6 have a vulnerability (CWE-400) related to uncontrolled resource consumption. When a binding is created on an x-jms-topic exchange, the server processes the rjms_erlang_selector argument by tokenizing and parsing it, which interns every atom literal without length limits or reclamation. This allows an authenticated low-privilege AMQP user with appropriate permissions to crash the broker node by sending crafted selector strings in fewer than 100 bind calls, resulting in a cross-tenant denial of service. The vulnerability requires the rabbitmq_jms_topic_exchange plugin to be enabled. The issue is resolved in the specified fixed versions.
Potential Impact
An authenticated AMQP user with limited privileges confined to one virtual host can cause the entire RabbitMQ broker node to crash, resulting in a denial of service that affects all tenants on that node. This can be achieved with fewer than 100 crafted binding calls. The impact is significant as it leads to service disruption but does not involve privilege escalation or data compromise.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-67220: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
Description
CVE-2026-67220 is a medium severity vulnerability in rabbitmq-server affecting versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6. It involves uncontrolled resource consumption due to atom interning when creating bindings on x-jms-topic exchanges with crafted selector strings. An authenticated low-privilege AMQP user confined to a single vhost can cause a denial of service by crashing the broker node with fewer than 100 bind calls. The issue requires the rabbitmq_jms_topic_exchange plugin to be enabled and specific permissions on exchanges and queues. The vulnerability is fixed in the stated versions.
CVSS v4.0
Score 6.0medium
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 3.13.15, 4.0.20, 4.1.11, and 4.2.6 have a vulnerability (CWE-400) related to uncontrolled resource consumption. When a binding is created on an x-jms-topic exchange, the server processes the rjms_erlang_selector argument by tokenizing and parsing it, which interns every atom literal without length limits or reclamation. This allows an authenticated low-privilege AMQP user with appropriate permissions to crash the broker node by sending crafted selector strings in fewer than 100 bind calls, resulting in a cross-tenant denial of service. The vulnerability requires the rabbitmq_jms_topic_exchange plugin to be enabled. The issue is resolved in the specified fixed versions.
Potential Impact
An authenticated AMQP user with limited privileges confined to one virtual host can cause the entire RabbitMQ broker node to crash, resulting in a denial of service that affects all tenants on that node. This can be achieved with fewer than 100 crafted binding calls. The impact is significant as it leads to service disruption but does not involve privilege escalation or data compromise.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor 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: 6ab43797f7a7c541064a9655
Added to database: 09/23/2026, 20:33:27 UTC
Last enriched: 09/23/2026, 20:48:20 UTC
Last updated: 09/23/2026, 23:24:54 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.