RabbitMQ: Atom table exhaustion via management API node field
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.
- Products
- rabbitmq
- Affected versions
- Not specified
- Fixed versions
- 3.13.15, 4.0.20, 4.1.11, 4.2.6
- CVEs
- CVE-2026-66073
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 28 Oct 2026, 12:32 UTC · Revision 1
Source evidence
RabbitMQ: Atom table exhaustion via management API node field
core-osv · Original sourcePublished 1 Oct 2026, 09:32 UTC
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.
osv:BIT-rabbitmq-2026-66073
rabbitmq
Fixed versions: 3.13.15, 4.0.20, 4.1.11, 4.2.6
Complete source record
{
"id": "5dc0b44b707a23041da85c0b3a337b3c1958b641ce77c04f00fa1a8db8bc7e8d",
"url": "https://osv.dev/vulnerability/BIT-rabbitmq-2026-66073",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ: Atom table exhaustion via management API node field",
"summary": "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.",
"evidence": "osv:BIT-rabbitmq-2026-66073",
"products": [
{
"name": {
"value": "rabbitmq",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.13.15",
"evidence": "/affected/0/ranges"
},
{
"value": "4.0.20",
"evidence": "/affected/0/ranges"
},
{
"value": "4.1.11",
"evidence": "/affected/0/ranges"
},
{
"value": "4.2.6",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "BIT-rabbitmq-2026-66073",
"aliases": [
"BIT-rabbitmq-2026-66073",
"CVE-2026-66073",
"GHSA-6v53-r759-jrvx"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.15"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.20"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.11"
},
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.6"
}
]
}
],
"package": {
"name": "rabbitmq",
"purl": "pkg:bitnami/rabbitmq",
"ecosystem": "Bitnami"
},
"severity": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/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"
}
],
"database_specific": {
"source": "https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-66073.json"
}
}
],
"modified": "2026-10-09T12:00:12.763309974Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/commit/7f64311471840e68f8cae09e4d4fdc4c8aca9229",
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6v53-r759-jrvx",
"https://nvd.nist.gov/vuln/detail/CVE-2026-66073"
],
"provider_metadata": {
"cpes": [
"cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
],
"severity": "Medium"
}
},
"related_cves": [
{
"value": "CVE-2026-66073",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 120698,
"published_at": "2026-10-01T09:32:49.94+00:00"
}