6.3Medium
CVE-2026-67225RabbitMQ: Stream-protocol frame length never validated against frame_max
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.
Weakness (CWE):
CWE-770
Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.
Affected products and versions
| Vendor | Product | Versions | |
|---|---|---|---|
| broadcom | rabbitmq server | 3.13.0 – < 3.13.15 | |
| rabbitmq | rabbitmq-server | >= 3.13.0, < 3.13.15, >= 4.0.0, < 4.0.20, >= 4.1.0, < 4.1.11, >= 4.2.0, < 4.2.6 |
References and patches
CPE matches (NVD) (4)
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*≥ 3.13.0 < 3.13.15cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*≥ 4.0.0 < 4.0.20cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*≥ 4.1.0 < 4.1.11cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*≥ 4.2.0 < 4.2.6