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

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

Timeline

1. Sep 23, 2026, 8:46 PM UTCCVE published
2. Sep 24, 2026, 2:08 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Sep 24, 2026, 2:08 PM UTCRecord last updated

Affected versions

• rabbitmq rabbitmq-server

  From 4.0.0 · fixed in 4.0.22; From 4.1.0 · fixed in 4.1.11; From 4.2.0 · fixed in 4.2.6

• rabbitmqBitnami

  From 4.0.0 · fixed in 4.0.22; From 4.1.0 · fixed in 4.1.11; From 4.2.0 · fixed in 4.2.6

References 3