RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service

Summary

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.

Timeline

1. Sep 25, 2026, 4:35 PM UTCCVE published
2. Sep 25, 2026, 7:09 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: partial

3. Sep 25, 2026, 7:09 PM UTCRecord last updated

Affected versions

• rabbitmq rabbitmq-server

  From 4.3.0 · fixed in 4.3.3; From 4.2.0 · fixed in 4.2.9; From 4.1.0 · fixed in 4.1.11

• rabbitmqBitnami

  From 4.1.0 · fixed in 4.1.11; From 4.2.0 · fixed in 4.2.9; From 4.3.0 · fixed in 4.3.3

References 5