CVE-2026-66072: RabbitMQ: Atom table exhaustion via stream `chunk_selector`

Published Sep 23, 2026
·
Updated

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, getchunkselector/1 calls binarytoatom on the raw client-supplied <<"chunkselector">> property from post-auth subscribe and resolveoffsetspec frames, with no whitelist and no existing guard. An authenticated stream client with read access to any stream can crash the broker node. Preconditions include rabbitmqstream plugin enabled Authenticated stream-protocol user with read access to at least one stream. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.

Affected Software

1 affected component
RabbitMQ RabbitMQ<3.13.15, <4.0.20, <4.1.11, <4.2.6, <4.3.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 3.13.15
  2. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.0.20
  3. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.1.11
  4. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.2.6
  5. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.3.1

Event History

Sep 23, 2026
CVE Published
via MITRE·08:13 PM
Data Sourced
via MITRE·08:13 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated client using the RabbitMQ stream protocol can exploit it if the rabbitmq_stream plugin is enabled and that user has read access to at least one stream. No access beyond stream read permission is stated as necessary.

2

What is the impact of successful exploitation?

An attacker can exhaust the Erlang atom table by supplying raw chunk_selector values, causing the RabbitMQ broker node to crash.

3

Are default RabbitMQ deployments affected?

The issue requires the rabbitmq_stream plugin to be enabled and a stream-protocol user with read access to a stream. Deployments without the plugin enabled or without such user access do not meet the listed preconditions.

4

Which versions contain the fix?

Fixed versions are 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1. Versions earlier than the applicable fixed release are affected.

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