Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-c8c4-gvv4-8
FAQ
What is CVE-2026-67225?
CVE-2026-67225 is a documented vulnerability. 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 compa...
How severe is CVE-2026-67225?
CVSS scoring is not yet available for CVE-2026-67225. Check NVD for updates.
Is there a patch for CVE-2026-67225?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.