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, get_chunk_selector/1 calls binary_to_atom on the raw client-supplied <<"chunk_selector">> property from post-auth subscribe and resolve_offset_spec 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 rabbitmq_stream 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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-48hm-chgv-398r Vendor Advisory
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-48hm-chgv-398r Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.0 · broadcomNVD modified 2026-10-19 20:37
Affected (CPE criteria) 1
cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*
References 4
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6 Release Notes
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1 Release Notes
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-48hm-chgv-398r Vendor Advisory
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-48hm-chgv-398r Vendor Advisory