All vulnerabilities
CVE-2026-67225GHSA-c8c4-gvv4-8j3q

rabbitmq-server: RabbitMQ: Stream-protocol frame length never validated against frame_max

rabbitmq rabbitmq-server
Open in ThreatlineRecord JSON
CVSS
6.3Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.34%Chance of exploitation activity in the next 30 days, higher than 26% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
Published25 Sep 2026Updated 25 Sep 2026CVE List

What fixes it

No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.

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.

Text from CVE List

Affected versions 4

  • rabbitmq-serveraffected: >= 3.13.0, < 3.13.15CVE List
  • rabbitmq-serveraffected: >= 4.0.0, < 4.0.20CVE List
  • rabbitmq-serveraffected: >= 4.1.0, < 4.1.11CVE List
  • rabbitmq-serveraffected: >= 4.2.0, < 4.2.6CVE List

References 2