Back

MEDIUM

RabbitMQ: Super-stream partitions unbounded allocation

Published Sep 23, 2026

Description

RabbitMQ is a messaging and streaming broker. Prior to versions 4.1.11, 4.2.6, and 4.3.0, validate_partitions only checks that the requested partition count is at least 1, with no upper bound. A large count such as lists:seq(0, 500000000) allocates roughly 8GB. Preconditions include The rabbitmq_stream_management plugin must be enabled. The caller needs the management tag and access to the target vhost.. This issue is fixed in versions 4.1.11, 4.2.6, and 4.3.0.

Affected products

Remediation

Red Hat statement

Red Hat rates this flaw MODERATE in products that ship affected RabbitMQ builds. With the stream-management plugin enabled, a management-tagged user with access to a virtual host can request an excessive number of super-stream partitions, exhausting broker memory and causing a denial of service.

Red Hat mitigation

Restrict management-tagged accounts and disable stream management where it is not needed.

References (8)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner GitHub_M
Published Sep 23, 2026
Updated Sep 24, 2026
Reserved Jul 23, 2026
CISA Vulnrichment
Updated Sep 24, 2026
NVD
Status Received
Modified Sep 23, 2026
Red Hat
Severity Moderate
Public date Sep 23, 2026
ENISA EUVD
Assigner GitHub_M
Published Sep 23, 2026
Updated Sep 24, 2026
Exploited since n/a
EUVD-2026-85637