CVE-2026-67218

Description

A flaw was found in RabbitMQ. A user with management tag and virtual host (vhost) access, but lacking configure permissions, can exploit a vulnerability in the HTTP API for super-stream creation. This flaw allows the user to bypass permission checks and create persistent cluster-wide resources, such as exchanges and partitioned stream queues. This leads to a privilege escalation, enabling a user with view-only access to create and manage resources.

Statement

Red Hat rates this flaw MODERATE in products that ship affected RabbitMQ builds. With stream management enabled, a user with management and virtual-host access but no configure permission can create persistent super-stream resources through the HTTP API, crossing the intended permission boundary.

Mitigation

Restrict that access or disable stream management where it is not needed.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.3N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactNoneN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Red Hat CVSS v3 Score Explanation

Independent review of GHSA-34jw-rm7g-hph4 and FIRST CVSS v3.1: authenticated read-only management/vhost access is PR:L, configured plugin assumed for base AC:L, same RabbitMQ authority S:U, constrained super-stream creation I:L; no demonstrated C/A impact. CVSS 4 AT:P and PR:H do not justify automatic v3 AC:H/PR:H conversion.

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Application Data; Read Files or Directories

An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.

Integrity

Technical Impact: Modify Application Data; Modify Files or Directories

An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.

Access Control

Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism

An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.

Frequently Asked Questions

Want to get errata notifications? Sign up here.