{"id":"CVE-2026-67218","title":"RabbitMQ is a messaging and streaming broker","summary":"RabbitMQ is a messaging and streaming broker. Prior to versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0, accept_content/2 at line 56 calls rabbit_stream_manager:create_super_stream/... directly after is_authorized (which only checks the managem…","severity":"low","cvss":2.1,"cvssVector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","cwe":["CWE-862"],"vendor":"rabbitmq","product":"rabbitmq-server","affected":["rabbitmq-server >= 4.0.0, < 4.0.22","rabbitmq-server >= 4.1.0, < 4.1.11","rabbitmq-server >= 4.2.0, < 4.2.6"],"published":"2026-09-23","updated":"2026-09-24","sourceUpdated":"2026-09-24T15:02:58.307","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-67218","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/releases/tag/v4.3.0","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-34jw-rm7g-hph4","label":"security-advisories@github.com"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-67218.json"},{"url":"https://access.redhat.com/security/cve/CVE-2026-67218"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2539778"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-67218"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-67218"},{"url":"https://access.redhat.com/errata/RHSA-2026:67552"}],"tags":["nvd","cve.org","csaf","vex","red-hat","score-dispute"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-09-24T14:08:46.026271Z"},"cvssSource":"cna","ingestedAt":"2026-09-23T21:33:13.528Z","patched":["hardened_images"],"scores":{"cna":2.1,"vendor":4.3},"epss":0.00373,"epssPercentile":0.3104,"slug":"CVE-2026-67218","body":"## Overview\n\nRabbitMQ is a messaging and streaming broker. Prior to versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0, accept_content/2 at line 56 calls rabbit_stream_manager:create_super_stream/... directly after is_authorized (which only checks the management tag + vhost access via is_authorized_vhost). The stream-protocol equivalent (rabbit_stream_reader.erl create_super_stream handler) calls rabbit_stream_utils:check_super_stream_management_permitted/4 which enforces configure on the exchange and each partition queue. The HTTP handler omits this call entirely. A user with management tag and vhost access , but no configure permission on any resource , can create super-streams (an exchange + N partition stream queues + bindings) via the HTTP API. The native stream-protocol path enforces configure on each resource; the HTTP path does not, creating a privilege escalation from 'can view' to 'can create persistent cluster-wide resources.' Preconditions include rabbitmq_stream_management plugin enabled management tag + vhost access (no resource permissions needed). This issue is fixed in versions 4.0.22, 4.1.11, 4.2.6, and 4.3.0.\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 18.0 · no fix planned: Red Hat Hardened Images, Red Hat OpenStack Platform 18.0 · updated 2026-09-25 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-67218.json)","depth":"sunlit","depthScore":12,"depthScoreParts":{"impact":11.6,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}