Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
2.1

CVE-2026-67218: RabbitMQ allows unauthorized creation of super‑streams via HTTP

CVE-2026-67218 · published 26 days ago
Summary

In certain older versions of RabbitMQ, a user who can only view the management console could create new super‑streams (a group of queues and an exchange) through the HTTP API, even though they lack permission to set up those resources. This could let a low‑privilege user add persistent messaging components across the cluster. Upgrade to the latest RabbitMQ release or apply the provided patch to restore proper permission checks.

What to do
  • Update debian rabbitmq-server to version 4.3.0-2.
  • Update rabbitmq to version 4.2.6.
Affected software
Ecosystem VendorProductAffected versions
– rabbitmq rabbitmq-server >= 4.0.0, < 4.0.22
Ubuntu:Pro:16.04:LTS canonical rabbitmq-server All versions
Debian:13 debian rabbitmq-server All versions
Debian:14 debian rabbitmq-server < 4.3.0-2
Fix: upgrade to 4.3.0-2
Bitnami – rabbitmq >= 4.2.0, < 4.2.6
Fix: upgrade to 4.2.6
– broadcom rabbitmq_server >= 4.0.0, < 4.0.22
>= 4.1.0, < 4.1.11
>= 4.2.0, < 4.2.6
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*
Original advisory text
RabbitMQ: Super-stream HTTP creation skips configure-permission check
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.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
2.1 Low
Exploitation
<1% chance of attack within 30 days
Type
CWE-862Missing Authorization
Timeline
Published23 Sep 2026
Updated19 Oct 2026
First seen23 Sep 2026
Track software like this
Free during beta