RabbitMQ: Super-stream HTTP creation skips configure-permission check (CVE-2026-67218) | HOL Guard CVE

Low · CVSS 2.1CVE-2026-67218

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

Answer in brief

CVE-2026-67218 records a Low severity (CVSS 2.1) vulnerability in RabbitMQ: Super-stream HTTP creation skips configure-permission check. The current sources do not mark it as known exploited. The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 23, 2026Updated Sep 23, 2026Source checked Sep 23, 2026First seen by HOL Sep 23, 2026Material review Sep 23, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
rabbitmq/rabbitmq-servergeneric	>=4.0.0 <4.0.22 \|\| >=4.1.0 <4.1.11 \|\| >=4.2.0 <4.2.6	4.0.22, 4.1.11, 4.2.6

Recommended response

Check inventory. Check lockfiles and deployed manifests for rabbitmq/rabbitmq-server.
Review the reported fix. Update rabbitmq/rabbitmq-server to 4.0.22 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 23, 2026

Sources and claim methodology

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

Quoted source text, attributed separately from HOL analysis.