CVE-2026-67218 RabbitMQ: Super-stream HTTP creation skips configure-permission check

What is CVE-2026-67218?

CVE-2026-67218 is a low-severity missing authorization vulnerability in Broadcom Rabbitmq Server, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official description

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 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.

Weakness: CWE-862

Which versions are affected by CVE-2026-67218?

1 open source package ship an affected version, including rabbitmq. It affects 1 product.

Products include Broadcom Rabbitmq Server.

How do I fix CVE-2026-67218?

Upgrade rabbitmq to a fixed version for your release line: 4.0.22, 4.1.11 or 4.2.6.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-67218 being exploited?

There is no known exploitation of CVE-2026-67218 in the wild and no public exploit code.

Other vulnerabilities in Broadcom Rabbitmq Server

• CVE-2016-9877 Auth bypass in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6; RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12 and 1.7.x before 1.7.7 Critical 9.8
• CVE-2026-67404 RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch Critical 9.2
• CVE-2026-67231 RabbitMQ: Trust-store whitelist by Issuer+Serial only Critical 9.1
• CVE-2026-57219 Information disclosure in rabbitmq-server High 8.7
• CVE-2026-67236 RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login High 8.2

All Broadcom Rabbitmq Server vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as BIT-rabbitmq-2026-67218, DEBIAN-CVE-2026-67218, GHSA-34jw-rm7g-hph4, UBUNTU-CVE-2026-67218.