CVE-2026-67225

RabbitMQ: Stream-protocol frame length never validated against frame_max

  • Medium 6.3

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.

Key facts

Published
25 Sep 2026
Last changed
25 Sep 2026
Assigned by
GitHub_M
EPSS
0.343% likely to be exploited in the next 30 days, higher than 28.323% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.3CVSS 4.0, Mediumfrom the CNA (GitHub_M)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
rabbitmqrabbitmq-server
  • >= 3.13.0, < 3.13.15 (affected)
  • >= 4.0.0, < 4.0.20 (affected)
  • >= 4.1.0, < 4.1.11 (affected)
  • >= 4.2.0, < 4.2.6 (affected)

Timeline

  1. 25 Sep 2026 Published

Weakness

References