CVE-2026-67218

published 23 Sep 2026 · updated 24 Sep 2026

RabbitMQ: Super-stream HTTP creation skips configure-permission check

2.1LowCVSS 2.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=4.0.0 <4.0.22, >=4.1.0 <4.1.11, >=4.2.0 <4.2.6

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67218 severity on Zeptric[![CVE-2026-67218](https://zeptric.io/badge/cve/CVE-2026-67218.svg)](https://zeptric.io/cve/CVE-2026-67218)