CVE-2026-67225

published 25 Sep 2026 · updated 17 Oct 2026

RabbitMQ: Stream-protocol frame length never validated against frame_max

6.3MediumCVSS 6.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=3.13.0 <3.13.15, >=4.0.0 <4.0.20, >=4.1.0 <4.1.11, >=4.2.0 <4.2.6

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67225 severity on Zeptric[![CVE-2026-67225](https://zeptric.io/badge/cve/CVE-2026-67225.svg)](https://zeptric.io/cve/CVE-2026-67225)