Back to CVE records
Medium 6.3Published Sep 25, 2026

CVE-2026-67225RabbitMQ: Stream-protocol frame length never validated against frame_max

Updated under an hour ago ()

Does this affect you?

It affects rabbitmq-server. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
6.3 MEDIUM (v4.0, CNA)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
Weakness (CWE)
CWE-770
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Undergoing Analysis
Record last updated
Sep 25, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
rabbitmq rabbitmq-server
rabbitmq:server (from the name)
from 3.13.0, < 3.13.15; from 4.0.0, < 4.0.20; from 4.1.0, < 4.1.11; from 4.2.0, < 4.2.6
CNA record

References

  • x-refsource-confirm
  • x-refsource-misc

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.