Security fix · CVE-2026-67225
RabbitMQ is a messaging and streaming broker.
Published Sep 25, 2026 · catalog updated Oct 20, 2026 · rabbitmq server
Last checked Oct 23, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-67225. EPSS is 0.34%. Act only if a listed version of rabbitmq server is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-67234 · Low
- CVE-2026-67230 · Medium
- CVE-2026-67227 · Medium
- CVE-2026-67226 · Medium
- CVE-2026-67237 · High
- Severity
- Medium6.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.34%
- Remediation
- Version ranges on file
- Affected products
- cpe broadcom/rabbitmq server
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe broadcom/rabbitmq server< 3.13.15
- cpe broadcom/rabbitmq server< 4.0.20
- cpe broadcom/rabbitmq server< 4.1.11
- cpe broadcom/rabbitmq server< 4.2.6
How to fix CVE-2026-67225
Upgrade
CVE-2026-67225 lists a fix boundary at 3.13.15. Compare the installed build with that boundary before you change production.
Version check
Affected < 3.13.15
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-67225. EPSS is 0.34%. Act only if a listed version of rabbitmq server is installed.
Which versions are affected?
Compare what you have installed with broadcom/rabbitmq server < 3.13.15; broadcom/rabbitmq server < 4.0.20; broadcom/rabbitmq server < 4.1.11; broadcom/rabbitmq server < 4.2.6. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-770: Allocation of Resources Without Limits or Throttling. EPSS 0.34%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 25, 2026 · NIST NVD
Detected
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 decla
Oct 20, 2026 · NIST NVD
Updated
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 decla
Sources
- CVE.orgVulnerability recordCVE-2026-67225
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-67225
30-day exploitation probability 0.34%
first.org - NIST NVDVulnerability recordCVE-2026-67225
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 t
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 23, 2026
- CVE.orgOct 21, 2026
- NIST NVDOct 20, 2026