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

Published Sep 25, 2026
·
Updated

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.

Affected Software

1 affected component
RabbitMQ RabbitMQ>=4.1.0<4.1.11, >=4.2.0<4.2.9, >=4.3.0<4.3.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.3.3
  2. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.2.9
  3. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.1.11

Event History

Sep 25, 2026
CVE Published
via MITRE·04:35 PM
Data Sourced
via MITRE·04:35 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial of service?

Deployments running RabbitMQ 4.1.0 through the fixed releases are affected when the rabbitmqstreammanagement feature is enabled and a management user can access a target virtual host. The described impact is especially significant for memory-limited nodes or containers.

2

What access does an attacker need?

An attacker needs an authenticated low-privileged management user account with access to the target virtual host. Configure, write, and read permissions are not required because allocation occurs before the resource-permission check.

3

Are default permissions sufficient to exploit this issue?

No. The attacker must be able to authenticate to the management API and access the target virtual host, but does not need permissions to configure, write to, or read from the resulting streams.

4

How can this be mitigated before upgrading?

Restrict management API access and ensure low-privileged management users do not have access to virtual hosts they do not need. Disabling rabbitmqstreammanagement also removes the affected feature path.

5

Which versions contain the fix?

The issue is fixed in RabbitMQ 4.3.3, 4.2.9, and 4.1.11.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203