CVE-2026-66073

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 28, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
Patch available. Sources: github_commit, github_release, github.
github_release Patch Available

RabbitMQ 4.2.6

Patch available: rabbitmq/rabbitmq-server v4.2.6

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
github_commit

commit 7f6431147184 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 7f6431147184 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/7f64311471840e68f8cae09e4d4fdc4c8aca9229
github Patch Available

Atom table exhaustion via management API node field · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6v53-r759-jrvx

Vendor Advisories for CVE-2026-66073(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 01:58 UTCEG score recompute
  2. 2026-10-04 01:58 UTCVendor advisory
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-03 04:07 UTCEG score recompute
  5. 2026-10-03 04:07 UTCVendor advisory
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 06:15 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 08:24 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-30 10:33 UTCEG score recompute
  12. 2026-09-29 12:36 UTCEG score recompute
  13. 2026-09-28 14:45 UTCEG score recompute
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-28 11:12 UTCEG score recompute
  16. 2026-09-27 13:21 UTCEG score recompute
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-25 17:37 UTCEG score recompute
  19. 2026-09-25 16:50 UTCEG score recompute
  20. 2026-09-25 16:24 UTCEG score recompute
  21. 2026-09-25 16:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-66073?
CVE-2026-66073 is a medium vulnerability published on September 25, 2026. 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 →…
When was CVE-2026-66073 disclosed?
CVE-2026-66073 was first published on September 25, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66073 actively exploited?
CVE-2026-66073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66073?
CVE-2026-66073 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66073?
A fix for CVE-2026-66073 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-66073 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-66073

Explore →

Is Your Infrastructure Affected by CVE-2026-66073?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs