All vulnerabilities

Servers and applications

CVE-2026-67225

Stream-protocol frame length never validated against frame_max

Severity
Medium 6.3
Published
9 Jul 2026
Last changed
20 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.13.15, 4.0.20, 4.1.11, 4.2.6
Exploit chance
0.3% in the next 30 daysHigher than 28% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Allocation without limits (CWE-770)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Slow it down
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-c8c4-gvv4-8j3q
Sources
NVD, Project advisories (GitHub)

Description

This vulnerability was identified by Team RabbitMQ and/or other teams at Broadcom, not via a responsible disclosure from an external researcher.

The frame size limit negotiated during the stream-protocol handshake is never enforced against the declared length of inbound frames. A client can send a frame whose declared size exceeds the negotiated frame_max, and the broker buffers the frame data before any size check is applied. This produces memory pressure on the node and a potential denial of service. The condition is reachable before authentication over the network.

The stream protocol negotiates a maximum frame size (FrameMax) during the Tune handshake. The negotiated value is stored but never applied to incoming frames. A %% TODO: check max frame size comment in rabbit_stream_core (deps/rabbitmq_stream_common/src/rabbit_stream_core.erl) confirmed the gap: the 4-byte frame size header is read and the frame is buffered without comparing the declared length against frame_max.

From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 3.13.0 before 3.13.15
  • From 4.0.0 before 4.0.20
  • From 4.1.0 before 4.1.11
  • From 4.2.0 before 4.2.6
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 3.13.0 before 3.13.15
  • From 4.0.0 before 4.0.20
  • From 4.1.0 before 4.1.11
  • From 4.2.0 before 4.2.6

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
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

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-67225
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67225
  • GitHub Advisory Database https://github.com/advisories/GHSA-c8c4-gvv4-8j3q
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-c8c4-gvv4-8j3q