CVE Catalog

CVE-2026-67408

MediumCVSS 6.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.34%

26th percentile - higher than 26% of all known CVEs

Summary

Vulnerability in RabbitMQ from 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, allowing low-privilege node denial of service via stream management super-stream binding keys allocation. The handler accepts PUT /api/stream/super-streams/{vhost}/{name} from an authenticated management user with access to the target vhost. When the request body contains the binding-keys field, the handler parses the attacker-controlled comma-separated string and builds the full stream-name list before checking whether the user has permission to configure the resulting streams. A low-privileged management user with vhost access can force large transient allocations. In a 768 MB memory-limited container, one HTTP PUT with about 4.5 MB of JSON body killed the container.

Risk Assessment

The attack can cause RabbitMQ node crash, leading to denial of service.

Recommendation

Update RabbitMQ to version 4.3.3, 4.2.9, or 4.1.11 (or later) and restrict management user permissions.

Related vulnerabilities

Original NVD description (English source)

RabbitMQ is a messaging and streaming broker. From 4.1.0 until 4.3.3, 4.2.9, and 4.1.11, Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service. rabbitMQ 4.3.1 with rabbitmqstreammanagement enabled accepts PUT /api/stream/super-streams/{vhost}/{name} requests from an authenticated management user that can access the target vhost. When the request body contains the binding-keys field, the handler parses the attacker-controlled comma-separated string and builds the full stream-name list before checking whether the user has permission to configure the resulting streams. A low-privileged management user with vhost access but no configure, write, or read permission can therefore force large transient allocations before the resource permission check. In a 768 MB memory-limited container, one HTTP PUT with about 4.5 MB of JSON body killed the RabbitMQ container with Docker state exited true An authenticated low-privileged management user can kill a memory-limited RabbitMQ node with one HTTP This issue is fixed in versions 4.3.3, 4.2.9, and 4.1.11.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS