CVE-2026-67230: CWE-770: Allocation of Resources Without Limits or Throttling 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, the Web STOMP WebSocket handler enforced neither max_frame_size nor login_timeout before authentication, allowing an unauthenticated client to keep a connection alive with a slow stream of small frames and accumulate unbounded pre-authentication state. The rabbitmq_web_stomp plugin must be enabled, and no authentication is required to reach the vulnerable path. 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 resource allocation vulnerability (CWE-770) in the Web STOMP WebSocket handler when the rabbitmq_web_stomp plugin is enabled. The handler fails to enforce max_frame_size and login_timeout limits before authentication, enabling unauthenticated clients to keep connections alive indefinitely with slow streams of small frames. This allows accumulation of unbounded pre-authentication state, potentially leading to resource exhaustion. No authentication is required to reach the vulnerable code path. The issue is resolved in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to maintain persistent connections with slow frame streams, causing the server to accumulate unbounded pre-authentication state. This can lead to resource exhaustion on the affected RabbitMQ server, potentially degrading service availability or causing denial of service conditions.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to these or later versions to remediate the issue. If upgrading is not immediately possible, consider disabling the rabbitmq_web_stomp plugin to prevent exposure to the vulnerable Web STOMP WebSocket handler. Monitor vendor advisories for any additional guidance.
CVE-2026-67230: CWE-770: Allocation of Resources Without Limits or Throttling 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, the Web STOMP WebSocket handler enforced neither max_frame_size nor login_timeout before authentication, allowing an unauthenticated client to keep a connection alive with a slow stream of small frames and accumulate unbounded pre-authentication state. The rabbitmq_web_stomp plugin must be enabled, and no authentication is required to reach the vulnerable path. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
CVSS v4.0
Score 6.3medium
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 resource allocation vulnerability (CWE-770) in the Web STOMP WebSocket handler when the rabbitmq_web_stomp plugin is enabled. The handler fails to enforce max_frame_size and login_timeout limits before authentication, enabling unauthenticated clients to keep connections alive indefinitely with slow streams of small frames. This allows accumulation of unbounded pre-authentication state, potentially leading to resource exhaustion. No authentication is required to reach the vulnerable code path. The issue is resolved in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
An unauthenticated attacker can exploit this vulnerability to maintain persistent connections with slow frame streams, causing the server to accumulate unbounded pre-authentication state. This can lead to resource exhaustion on the affected RabbitMQ server, potentially degrading service availability or causing denial of service conditions.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to these or later versions to remediate the issue. If upgrading is not immediately possible, consider disabling the rabbitmq_web_stomp plugin to prevent exposure to the vulnerable Web STOMP WebSocket handler. 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: 6ab6a25af7a7c54106018e29
Added to database: 09/25/2026, 16:33:30 UTC
Last enriched: 09/25/2026, 16:48:42 UTC
Last updated: 09/26/2026, 03:44:40 UTC
Views: 12
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.