CVE-2026-67227

published 25 Sep 2026 · updated 17 Oct 2026

RabbitMQ: Atom exhaustion: to_atom on global-parameter :name

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=4.0.0 <4.0.22, >=4.1.0 <4.1.14, >=4.2.0 <4.2.7, >=4.3.0 <4.3.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67227 severity on Zeptric[![CVE-2026-67227](https://zeptric.io/badge/cve/CVE-2026-67227.svg)](https://zeptric.io/cve/CVE-2026-67227)