CVE-2026-57220: RabbitMQ: Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS
RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, the RabbitMQ stream listener does not enforce the configured stream frame-size limit while assembling frames during authentication and before Tune negotiation, allowing an unauthenticated remote client to declare oversized frame lengths and consume broker memory in rabbitstreamcore. This issue is fixed in version 4.2.6.
Other sources
RabbitMQ: Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.13.7-7 - Upgrade
Upgrade
RabbitMQ stream listenerto a version that resolves this vulnerability.Fixed in 4.2.6
Event History
Frequently Asked Questions
What is the severity of CVE-2026-57220?
The severity of CVE-2026-57220 is high with a CVSS score of 7.5.
How do I fix CVE-2026-57220?
To fix CVE-2026-57220, upgrade RabbitMQ to version 4.2.6 or later which enforces the configured stream frame-size limit.
What is the risk associated with CVE-2026-57220?
CVE-2026-57220 presents a risk of a denial-of-service (DoS) attack by allowing unauthorized clients to exhaust memory by declaring oversized frame lengths.
Which software is affected by CVE-2026-57220?
RabbitMQ versions prior to 4.2.6 are affected by CVE-2026-57220.
What type of attack does CVE-2026-57220 enable?
CVE-2026-57220 enables an unauthenticated memory-exhaust denial-of-service attack during authentication.