Resource exhaustion in Broadcom Rabbitmq Server
CVE-2026-67227
RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1, Atom exhaustion: toatom on global-parameter :name. resourceexists/2 (and the PUT/DELETE handlers) call rabbitdatacoercion:toatom/1 on the :name URL path segment. toatom/1 uses binarytoatom/2 (unsafe). The endpoint requires policymaker (not management, but below A user with the policymaker tag can crash the node by exhausting the atom table via repeated requests to /api/global-parameters/:name with unique :name Management plugin enabled policymaker tag ~1M HTTP. This issue is fixed in versions 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.9 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.004, 32.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Broadcom Rabbitmq Server
- Rabbitmq Rabbitmq-Server — versions >= 4.0.0, < 4.0.22, >= 4.1.0, < 4.1.14, >= 4.2.0, < 4.2.7
Weakness classification (CWE)
References
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q7x8-97rh-cr24 (Vendor Advisory)
- https://github.com/rabbitmq/rabbitmq-server/commit/8fbe6d8112427e85fb9a9206b3eb6e9a3ddd3e39 (Patch)
- https://github.com/rabbitmq/rabbitmq-server/commit/fc591e7ee27a29657ca960930acefd3e4217e007 (Patch)
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.7 (Patch, Release Notes)
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1 (Patch, Release Notes)