CVE-2026-67225

RabbitMQ: Stream-protocol frame length never validated against frame_max

State: Published
Severity: 6.3 Medium
Published: Sep 25, 2026
Updated: Sep 25, 2026
Reserved: Jul 28, 2026

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.

Scores

CVSS	Score	Vector	Source
4.0	6.3 Medium	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	GitHub_M

Weaknesses

CWE-770 Allocation of Resources Without Limits or Throttling

Affected Products

Product	Versions
rabbitmq-serverrabbitmq	>= 3.13.0, < 3.13.15Affected >= 4.0.0, < 4.0.20Affected >= 4.1.0, < 4.1.11Affected >= 4.2.0, < 4.2.6Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.