{"id":"CVE-2026-67225","title":"RabbitMQ is a messaging and streaming broker","summary":"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 declare…","severity":"medium","cvss":6.3,"cvssVector":"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","cwe":["CWE-770"],"vendor":"rabbitmq","product":"rabbitmq-server","affected":["rabbitmq-server >= 3.13.0, < 3.13.15","rabbitmq-server >= 4.0.0, < 4.0.20","rabbitmq-server >= 4.1.0, < 4.1.11","rabbitmq-server >= 4.2.0, < 4.2.6"],"published":"2026-09-25","updated":"2026-09-28","sourceUpdated":"2026-09-28T14:38:38.163","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-67225","references":[{"url":"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-c8c4-gvv4-8j3q","label":"security-advisories@github.com"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-67225.json"},{"url":"https://access.redhat.com/security/cve/CVE-2026-67225"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2541500"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-67225"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-67225"},{"url":"https://access.redhat.com/errata/RHSA-2026:67552"}],"tags":["nvd","cve.org","csaf","vex","red-hat"],"epss":0.00343,"epssPercentile":0.27703,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-09-25T16:42:24.094993Z"},"cvssSource":"cna","ingestedAt":"2026-09-25T17:13:14.017Z","patched":["hardened_images"],"scores":{"cna":6.3,"vendor":5.3},"slug":"CVE-2026-67225","body":"## Overview\n\nRabbitMQ 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Vendor advisories\n\n- **RHSA-2026:67552** · Red Hat · fixed in: Red Hat Hardened Images · released 2026-09-15 · [advisory](https://access.redhat.com/errata/RHSA-2026:67552)\n- **Red Hat VEX** · Moderate · affected: Red Hat Hardened Images, Red Hat OpenStack Platform 13 (Queens), Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1, Red Hat OpenStack Platform 18.0 · no fix planned: Red Hat OpenStack Platform 13 (Queens), Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1, Red Hat Hardened Images, … · updated 2026-10-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-67225.json)","depth":"sunlit","depthScore":35,"depthScoreParts":{"impact":34.7,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}