CVE-2026-66080: CWE-770: Allocation of Resources Without Limits or Throttling in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. Prior to versions 4.1.11, 4.2.6, and 4.3.0, validate_partitions only checks that the requested partition count is at least 1, with no upper bound. A large count such as lists:seq(0, 500000000) allocates roughly 8GB. Preconditions include The rabbitmq_stream_management plugin must be enabled. The caller needs the management tag and access to the target vhost.. This issue is fixed in versions 4.1.11, 4.2.6, and 4.3.0.
AI Analysis
Technical Summary
RabbitMQ versions prior to 4.1.11, 4.2.6, and 4.3.0 contain a resource allocation vulnerability (CWE-770) in the validate_partitions function. The function validates that the requested partition count is at least 1 but does not impose an upper limit, allowing a malicious caller with management privileges and access to the target vhost to request an extremely large partition count (e.g., lists:seq(0, 500000000)) which results in approximately 8GB of memory allocation. This can lead to resource exhaustion. The vulnerability requires the rabbitmq_stream_management plugin to be enabled. Fixed in versions 4.1.11, 4.2.6, and 4.3.0.
Potential Impact
An attacker with management tag and access to the target virtual host, and with the rabbitmq_stream_management plugin enabled, can cause excessive memory allocation by requesting a very large partition count. This can lead to resource exhaustion on the server, potentially impacting availability or performance. There is no indication of remote code execution or data compromise from this vulnerability.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 4.1.11, 4.2.6, and 4.3.0. Users should upgrade to one of these versions or later to remediate the issue. No other mitigations are indicated.
CVE-2026-66080: CWE-770: Allocation of Resources Without Limits or Throttling in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. Prior to versions 4.1.11, 4.2.6, and 4.3.0, validate_partitions only checks that the requested partition count is at least 1, with no upper bound. A large count such as lists:seq(0, 500000000) allocates roughly 8GB. Preconditions include The rabbitmq_stream_management plugin must be enabled. The caller needs the management tag and access to the target vhost.. This issue is fixed in versions 4.1.11, 4.2.6, and 4.3.0.
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 prior to 4.1.11, 4.2.6, and 4.3.0 contain a resource allocation vulnerability (CWE-770) in the validate_partitions function. The function validates that the requested partition count is at least 1 but does not impose an upper limit, allowing a malicious caller with management privileges and access to the target vhost to request an extremely large partition count (e.g., lists:seq(0, 500000000)) which results in approximately 8GB of memory allocation. This can lead to resource exhaustion. The vulnerability requires the rabbitmq_stream_management plugin to be enabled. Fixed in versions 4.1.11, 4.2.6, and 4.3.0.
Potential Impact
An attacker with management tag and access to the target virtual host, and with the rabbitmq_stream_management plugin enabled, can cause excessive memory allocation by requesting a very large partition count. This can lead to resource exhaustion on the server, potentially impacting availability or performance. There is no indication of remote code execution or data compromise from this vulnerability.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 4.1.11, 4.2.6, and 4.3.0. Users should upgrade to one of these versions or later to remediate the issue. No other mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-23T23:25:28.898Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab43797f7a7c541064a9654
Added to database: 09/23/2026, 20:33:27 UTC
Last enriched: 09/23/2026, 20:48:29 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.