Privilege Escalation in RabbitMQ Stream Management

Publication date: 2026-09-23

Last updated on: 2026-09-23

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-23

Last Modified

2026-09-23

Generated

2026-09-24

AI Q&A

2026-09-24

EPSS Evaluated

N/A

NVD

CVE-2026-67218

Affected Vendors & Products

Vendor	Product	Version / Range
rabbitmq	rabbitmq	to 4.3.0 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability in RabbitMQ allows users with only management tag and vhost access to create super-streams via the HTTP API without needing configure permissions on any resource. The native stream-protocol path enforces proper permissions, but the HTTP path omits these checks, enabling privilege escalation from view-only to resource creation.

Impact Analysis

An attacker with limited access could create persistent cluster-wide resources (super-streams) that consume system resources, disrupt operations, or lead to denial of service. This bypasses intended permission restrictions and could allow unauthorized resource creation.

Mitigation Strategies

Upgrade RabbitMQ to versions 4.0.22, 4.1.11, 4.2.6, or 4.3.0 or later to address the privilege escalation issue in the HTTP API for super-stream creation.

Hi! I’m here to help you understand CVE-2026-67218. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70