CVE-2026-66072: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, get_chunk_selector/1 calls binary_to_atom on the raw client-supplied <<"chunk_selector">> property from post-auth subscribe and resolve_offset_spec frames, with no whitelist and no existing guard. An authenticated stream client with read access to any stream can crash the broker node. Preconditions include rabbitmq_stream plugin enabled Authenticated stream-protocol user with read access to at least one stream. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-66072) in rabbitmq-server arises from the get_chunk_selector/1 function calling binary_to_atom on a raw client-supplied chunk_selector property without a whitelist or guard. This occurs in post-auth subscribe and resolve_offset_spec frames when the rabbitmq_stream plugin is enabled. An authenticated stream client with read permissions can exploit this to crash the broker node by causing uncontrolled resource consumption. The vulnerability affects multiple version branches prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, where it has been fixed.
Potential Impact
An authenticated user with read access to any stream can crash the rabbitmq broker node, causing a denial of service due to uncontrolled resource consumption. This impacts availability but does not indicate confidentiality or integrity compromise. The vulnerability requires the rabbitmq_stream plugin to be enabled and user authentication with appropriate permissions.
Mitigation Recommendations
This issue is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-66072: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, get_chunk_selector/1 calls binary_to_atom on the raw client-supplied <<"chunk_selector">> property from post-auth subscribe and resolve_offset_spec frames, with no whitelist and no existing guard. An authenticated stream client with read access to any stream can crash the broker node. Preconditions include rabbitmq_stream plugin enabled Authenticated stream-protocol user with read access to at least one stream. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
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
This vulnerability (CVE-2026-66072) in rabbitmq-server arises from the get_chunk_selector/1 function calling binary_to_atom on a raw client-supplied chunk_selector property without a whitelist or guard. This occurs in post-auth subscribe and resolve_offset_spec frames when the rabbitmq_stream plugin is enabled. An authenticated stream client with read permissions can exploit this to crash the broker node by causing uncontrolled resource consumption. The vulnerability affects multiple version branches prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, where it has been fixed.
Potential Impact
An authenticated user with read access to any stream can crash the rabbitmq broker node, causing a denial of service due to uncontrolled resource consumption. This impacts availability but does not indicate confidentiality or integrity compromise. The vulnerability requires the rabbitmq_stream plugin to be enabled and user authentication with appropriate permissions.
Mitigation Recommendations
This issue is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1. Users should upgrade to these or later versions to remediate the vulnerability. 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-23T23:25:28.897Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab43797f7a7c541064a9652
Added to database: 09/23/2026, 20:33:27 UTC
Last enriched: 09/23/2026, 20:48:37 UTC
Last updated: 09/24/2026, 01:57:04 UTC
Views: 5
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.