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

Severity: medium (CVSS 6.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-09-23 · updated 2026-10-19
Weakness: CWE-862

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.

Affected products

rabbitmq-server: from 4.0.0 before 4.0.22; from 4.1.0 before 4.1.11; from 4.2.0 before 4.2.6 — fixed in 4.0.22, 4.1.11, 4.2.6

How to fix

Upgrade to a fixed version: rabbitmq-server 4.0.22, 4.1.11, 4.2.6. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-67218 or the next vulnerability affects your stack