CVE-2026-66073: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6, Atom table exhaustion via management API node field. pUT /api/queues/:vhost/:name (and the exchanges and bindings endpoints) accepts a node JSON field. The value goes through rabbitnodes:make → listtoatom with no cluster membership check first. Each unique value permanently leaks one atom. A March 2026 refactoring (ea61ce2563) introduced safe helpers in rabbitmgmtnodes.erl (parsenodename, safeatom, and requirenodename, using binarytoexistingatom) and fixed several callers (QQ replica ops, wmauthattempts, wmnodememoryets, getsortreverse, and rabbitfederationmgmt), but getnode/1 in rabbitmgmtutil.erl:880-885, the primary vector used by directrequest/6, was not Roughly 900K requests crash the VM via systemlimit, and all tenants lose Any user with the management tag and one vhost, the lowest privilege This issue is fixed in versions 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6.
AI Analysis
Technical Summary
RabbitMQ versions 3.13.0 through 3.13.14, 4.0.0 through 4.0.19, 4.1.0 through 4.1.10, and 4.2.0 through 4.2.5 are vulnerable to uncontrolled resource consumption (CWE-400) via atom table exhaustion. The vulnerability arises because the management API endpoints (queues, exchanges, bindings) accept a 'node' JSON field whose value is converted to an atom without verifying cluster membership, causing a permanent atom leak. A refactoring in March 2026 introduced safer atom handling in many places but missed the getnode/1 function used by directrequest/6, which remains vulnerable. Approximately 900,000 crafted requests can exhaust the atom table, crashing the Erlang VM and causing denial of service for all tenants. The vulnerability requires management privileges and access to at least one virtual host. Fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
Successful exploitation leads to exhaustion of the Erlang VM atom table, causing the VM to crash and resulting in denial of service for all tenants on the affected RabbitMQ server. The attack requires management privileges and access to at least one virtual host. There is no indication of remote code execution or data disclosure from the provided data.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
CVE-2026-66073: CWE-400: Uncontrolled Resource Consumption in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6, Atom table exhaustion via management API node field. pUT /api/queues/:vhost/:name (and the exchanges and bindings endpoints) accepts a node JSON field. The value goes through rabbitnodes:make → listtoatom with no cluster membership check first. Each unique value permanently leaks one atom. A March 2026 refactoring (ea61ce2563) introduced safe helpers in rabbitmgmtnodes.erl (parsenodename, safeatom, and requirenodename, using binarytoexistingatom) and fixed several callers (QQ replica ops, wmauthattempts, wmnodememoryets, getsortreverse, and rabbitfederationmgmt), but getnode/1 in rabbitmgmtutil.erl:880-885, the primary vector used by directrequest/6, was not Roughly 900K requests crash the VM via systemlimit, and all tenants lose Any user with the management tag and one vhost, the lowest privilege This issue is fixed in versions 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6.
CVSS v4.0
Score 6.0medium
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ versions 3.13.0 through 3.13.14, 4.0.0 through 4.0.19, 4.1.0 through 4.1.10, and 4.2.0 through 4.2.5 are vulnerable to uncontrolled resource consumption (CWE-400) via atom table exhaustion. The vulnerability arises because the management API endpoints (queues, exchanges, bindings) accept a 'node' JSON field whose value is converted to an atom without verifying cluster membership, causing a permanent atom leak. A refactoring in March 2026 introduced safer atom handling in many places but missed the getnode/1 function used by directrequest/6, which remains vulnerable. Approximately 900,000 crafted requests can exhaust the atom table, crashing the Erlang VM and causing denial of service for all tenants. The vulnerability requires management privileges and access to at least one virtual host. Fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
Successful exploitation leads to exhaustion of the Erlang VM atom table, causing the VM to crash and resulting in denial of service for all tenants on the affected RabbitMQ server. The attack requires management privileges and access to at least one virtual host. There is no indication of remote code execution or data disclosure from the provided data.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-23T23:25:28.897Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab6a25af7a7c54106018e24
Added to database: 09/25/2026, 16:33:30 UTC
Last enriched: 09/25/2026, 16:49:06 UTC
Last updated: 09/26/2026, 02:44:18 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.