CVE-2026-67408Medium· 6.5▾ TwilightPoC availableRabbitMQ 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 ena…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 35.8 · likelihood 0.1 · exploitation 12
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Sep 27.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Exploit / PoC code exists
0.3%
Last analysed / modified upstream
7.1 → 6.5
high → medium
0.3% → 0.4%
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.
rabbitmq_server >= 4.1.0, < 4.1.11rabbitmq_server >= 4.2.0, < 4.2.9rabbitmq_server >= 4.3.0, < 4.3.3Upgrade past the affected range:
rabbitmq_server 4.3.3Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-67415Medium· 4.9RabbitMQ is a messaging and streaming broker
CVE-2026-67241Medium· 6.5RabbitMQ is a messaging and streaming broker
CVE-2026-67242Medium· 5.4RabbitMQ is a messaging and streaming broker
CVE-2026-67409Medium· 6.5RabbitMQ is a messaging and streaming broker
CVE-2026-61837Medium· 5.3RabbitMQ is a messaging and streaming broker
CVE-2026-67413Medium· 6.5RabbitMQ is a messaging and streaming broker