CVEvulnerability
CVE-2026-67227
5.9 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-09-25
- Last modified
- 2026-10-20
- Assigner
- [email protected]
- CVSS 4.0 ([email protected])
- 5.9 MEDIUM — CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- CVSS 3.1 ([email protected])
- 4.9 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-400
Description
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 configurations
• broadcom rabbitmq server (>= 4.0.0 < 4.0.22)
• broadcom rabbitmq server (>= 4.1.0 < 4.1.14)
• broadcom rabbitmq server (>= 4.2.0 < 4.2.7)
• broadcom rabbitmq server (>= 4.3.0 < 4.3.1)
Related
Weakness · CWE (1)
- CWE-400 Uncontrolled Resource Consumption weakness
References
- 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 Release Notes, Patch
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1 Release Notes, Patch
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q7x8-97rh-cr24 Vendor Advisory