Servers and applications
CVE-2026-57220
Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS
- Severity
- High 7.5
- Published
- 24 Jun 2026
- Last changed
- 17 Nov 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.13.15, 4.0.20, 4.1.11, 4.2.6
- Exploit chance
- 0.5% in the next 30 daysHigher than 46% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Also known as
- GHSA-f364-87q5-j35q
- Sources
- NVD, Project advisories (GitHub)
Description
RabbitMQ 4.2.5's stream listener does not enforce the configured stream frame-size limit of 1 MiB while assembling frames during authentication/before Tune negotiation. A remote, fully unauthenticated client can therefore declare oversized frame lengths and stream large partial frames into rabbit_stream_core, which stores the incomplete payload in broker memory before authentication or vhost checks occur. The only deployment-specific prerequisite is use of the first-party rabbitmq_stream listener on port 5552; no RabbitMQ credentials, management access, or root-owned configuration control are required.
The stream server advertises and configures a default frame_max of 1 MiB via deps/rabbitmq_stream_common/include/rabbit_stream.hrl:85 and deps/rabbitmq_stream/src/rabbit_stream_sup.erl:58. The stream protocol documentation also describes FrameMax as the frame-size limit in bytes in deps/rabbitmq_stream/docs/PROTOCOL.adoc.
Affected software
| Software | Affected versions |
|---|---|
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server |
|
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server |
|
About RabbitMQ
open source message broker, sometimes referred to as "Rabbit"
- Docker Hub pulls
- 3,918,841,187Docker Hub, 15 Nov 2026
- GitHub stars
- 13,973GitHub, 15 Nov 2026
- Forks
- 4,032GitHub, 15 Nov 2026
- Latest release
- v4.4.0GitHub, 15 Nov 2026
- Released
- 19 Oct 2026GitHub
- Developer
- Jean-Sébastien PédronWikidata
- License
- Mozilla Public License, version 2.0Wikidata
- Written in
- ErlangWikidata
- First published on GitHub
- 20 Sept 2010GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.4 | 4.4.0 | Until 31 Jul 2027 |
| 4.3 | 4.3.7 | Until 31 Jan 2027 |
| 4.2 | 4.2.9 | Ended 31 Jul 2026 |
| 4.1 | 4.1.8 | Ended 30 Jan 2026 |
| 4.0 | 4.0.9 | Ended 30 Apr 2025 |
| 3.13 | 3.13.7 | Ended 30 Sept 2024 |
From endoflife.date.
Vulnerabilities in RabbitMQ
- In our list
- 107
- Published in the last 12 months
- 89
- Critical, last 12 months
- 4
- High, last 12 months
- 22
- Known exploited
- 0
- GHSA-3wxh-g236-vm46LDAP authentication failures allow unauthenticated log amplificationHigh 8.2 25 Oct 2026
- GHSA-g73v-gcjq-2g4hAMQP message conversion can repeatedly disconnect AMQP 0-9-1 consumersMedium 6.3 25 Oct 2026
- GHSA-6wvj-vwrc-wcrmHTML injection in management UI OAuth login warningMedium 5.7 25 Oct 2026
- GHSA-mhh3-4wv2-rrj7SASL credentials are not redacted from `amqp10_client` crash dumps and `sys:get_status` outputMedium 5.7 25 Oct 2026
- GHSA-9h6g-46wc-m2f5Memory DoS via incomplete AMQP 0-9-1 messagesHigh 7.1 25 Oct 2026
- GHSA-j6hc-926v-qwq2RabbitMQ STOMP consumers retain OAuth queue access after JWT expirationMedium 4.9 18 Sept 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-57220
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-57220
- GitHub Advisory Database https://github.com/advisories/GHSA-f364-87q5-j35q
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f364-87q5-j35q