GPU VulnDB

Database/Control plane, storage & DevOps

RabbitMQ: super-stream binding-keys parsed before the permission check, one PUT kills the node

CVSS 7.1CVE-2026-67408Control plane, storage & DevOpscurated

Impact

PUT /api/stream/super-streams/{vhost}/{name} parses the attacker-controlled comma-separated binding-keys string and materialises the full stream-name list before checking whether the caller has configure, write or read permission on the resulting streams. A management user with nothing more than access to the vhost can force a large transient allocation; the advisory reports a ~4.5 MB JSON body killing a 768 MB memory-limited RabbitMQ container outright. Where RabbitMQ is the queue between schedulers, job submission, or inference request fan-out, losing the broker stalls work across the cluster, and a container that exits has to be restarted and its state recovered.

Who can reach it

Any authenticated management-UI/API user with access to the target vhost - no configure, write or read permission needed. Requires the rabbitmq_stream_management plugin to be enabled.

What to do

Upgrade to RabbitMQ 4.3.3, 4.2.9 or 4.1.11 (affected from 4.1.0). Restart the broker node, rolling through the cluster. If you cannot patch now, disable rabbitmq_stream_management or block the super-streams endpoint at the proxy; raising the container memory limit only raises the bar.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.