CVE-2026-67225: 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 stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. 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 stream protocol. The FrameMax value negotiated during the Tune handshake is stored but not used to validate the size of inbound frames before buffering. Consequently, a remote client with no privileges can send an oversized frame that causes excessive memory usage, leading to denial of service. This issue is resolved in the specified fixed versions.
Potential Impact
A remote unauthenticated attacker can exploit this vulnerability to cause excessive memory pressure on the RabbitMQ server, potentially leading to denial of service conditions. There is no indication of data compromise or code execution from the provided data.
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. No other mitigation or temporary workaround is indicated in the available data.
CVE-2026-67225: 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 stream protocol stored the FrameMax value negotiated during the Tune handshake but did not compare it with an inbound frame's declared length before buffering the frame. With the stream plugin enabled, a remote client could therefore cause excessive memory pressure and denial of service by declaring an oversized frame. 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 stream protocol. The FrameMax value negotiated during the Tune handshake is stored but not used to validate the size of inbound frames before buffering. Consequently, a remote client with no privileges can send an oversized frame that causes excessive memory usage, leading to denial of service. This issue is resolved in the specified fixed versions.
Potential Impact
A remote unauthenticated attacker can exploit this vulnerability to cause excessive memory pressure on the RabbitMQ server, potentially leading to denial of service conditions. There is no indication of data compromise or code execution from the provided data.
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. No other mitigation or temporary workaround is indicated in the available data.
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: 6ab6a25af7a7c54106018e28
Added to database: 09/25/2026, 16:33:30 UTC
Last enriched: 09/25/2026, 16:48:46 UTC
Last updated: 09/26/2026, 03:44:32 UTC
Views: 14
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.