CVE-2026-67408 RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
- Technology
- DockerUbuntuDebianRed Hat
Description
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.
Upgrade path
10 packages: 3 fixed, 6 with no fix yet.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| redhat/rabbitmq-server(Red Hat openstack 13) | All versions | No fix listed | No fix yet |
| redhat/rabbitmq-server(Red Hat openstack 16.2) | All versions | No fix listed | No fix yet |
| redhat/rabbitmq-server(Red Hat openstack 17.1) | All versions | No fix listed | No fix yet |
| redhat/rabbitmq-server(Red Hat openstack 18.0) | All versions | No fix listed | No fix yet |
| redhat/rabbitmq-server4.2(Red Hat hummingbird 1) | All versions | No fix listed | No fix yet |
| ubuntu/rabbitmq-server(Ubuntu 26.10) | All versions | No fix listed | No fix yet |
| broadcom rabbitmq server | >= 4.1.0, < 4.1.11; >= 4.2.0, < 4.2.9; >= 4.3.0, < 4.3.3 | 4.1.11, 4.2.9, 4.3.3 | Fixed |
| debian/rabbitmq-server(Debian 14) | < 4.3.6-1; = 4.0.5-6; = 4.0.5-8; = 4.0.5-9 +13 more | 4.3.6-1 | Fixed |
| redhat/rabbitmq-server4-3-main(Red Hat hummingbird 1) | < 4.3.6-1.hum1 | 4.3.6-1.hum1 | Fixed |
| rabbitmq-server | = >= 4.1.0, < 4.1.11; = >= 4.2.0, < 4.2.9; = >= 4.3.0, < 4.3.3 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| redhat/rabbitmq-server4-3-main(Red Hat:hummingbird:1) | < 4.3.6-1.hum1 | 4.3.6-1.hum1 |
| redhat/rabbitmq-server4.2(Red Hat:hummingbird:1) | All versions | No fix listed |
| redhat/rabbitmq-server(Red Hat:openstack:13) | All versions | No fix listed |
| redhat/rabbitmq-server(Red Hat:openstack:16.2) | All versions | No fix listed |
| redhat/rabbitmq-server(Red Hat:openstack:17.1) | All versions | No fix listed |
| redhat/rabbitmq-server(Red Hat:openstack:18.0) | All versions | No fix listed |
| rabbitmq-server | = >= 4.3.0, < 4.3.3 | No fix listed |
| rabbitmq-server | = >= 4.2.0, < 4.2.9 | No fix listed |
| rabbitmq-server | = >= 4.1.0, < 4.1.11 | No fix listed |
| debian/rabbitmq-server(Debian:14) | < 4.3.6-1 | 4.3.6-1 |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-10 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-11 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-12 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-13 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-14 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-6 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-8 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.0.5-9 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.3.0-1 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.3.0-2 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.3.0-3 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.3.2-1 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.3.2-2 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.3.2-3 | No fix listed |
| debian/rabbitmq-server(Debian:14) | = 4.3.2-4 | No fix listed |
Show 5 more
| Product | Affected versions | Fixed in |
|---|---|---|
| debian/rabbitmq-server(Debian:14) | = 4.3.2-5 | No fix listed |
| ubuntu/rabbitmq-server(Ubuntu:26.10) | All versions | No fix listed |
| broadcom rabbitmq server | >= 4.1.0, < 4.1.11 | 4.1.11 |
| broadcom rabbitmq server | >= 4.2.0, < 4.2.9 | 4.2.9 |
| broadcom rabbitmq server | >= 4.3.0, < 4.3.3 | 4.3.3 |
References
- Red Hat CVE page vendor-advisory
- RHSA-2026:67552 patch vendor-advisory
- Red Hat Bugzilla 2541516 issue-tracking
- www.cve.org
- nvd.nist.gov
- github.com
- github.com
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9 release-notes
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3 release-notes
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-2hm4-4438-49q8 exploit vendor-advisory
- https://github.com/rabbitmq/rabbitmq-server/commit/0f3defd176e027f54f447beee168d906d4f109b6 patch
- https://github.com/rabbitmq/rabbitmq-server/commit/eb11bc44005fd6d327a78bf171bc598207778c9b patch
- Debian Security Tracker CVE-2026-67408 vendor-advisory
- Ubuntu CVE tracker vendor-advisory
- bugs.debian.org issue-tracking
- ENISA EUVD EUVD-2026-87241 third-party-advisory