CVE-2026-66073

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-87149 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: 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.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

October 8, 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 advisoryMentions a patch (unverified)

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(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrabbitmq-server4-3-main-4.3.6-1.hum12026-09-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server3.10.8-1.1 ... 4.3.6-1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.6-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.0-1 (9 versions)
  • every version up to 4.3.0-2: fixed in 4.3.0-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-30 07:55 UTCOSV refresh
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-25 14:11 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-22 19:37 UTCEG score recompute
  14. 2026-10-22 19:37 UTCVendor advisory
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-10-18 03:21 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 50 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-12 15:46 UTCEG score recompute
  3. 2026-10-11 19:31 UTCEG score recompute
  4. 2026-10-11 16:46 UTCEG score recompute
  5. 2026-10-11 14:07 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-11 09:12 UTCEG score recompute
  8. 2026-10-11 09:12 UTCVendor advisory
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-10 11:19 UTCEG score recompute
  11. 2026-10-10 11:19 UTCVendor advisory
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-09 13:28 UTCEG score recompute
  14. 2026-10-09 13:28 UTCVendor advisory
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-10-08 15:34 UTCEG score recompute▲ 0.50
  17. 2026-10-08 15:34 UTCVendor advisory
  18. 2026-10-08 15:34 UTCNVD updateCVSS v3 → 6.5
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-10-07 17:39 UTCVendor advisory
  21. 2026-10-06 19:38 UTCEG score recompute
  22. 2026-10-06 19:38 UTCVendor advisory
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-10-05 21:44 UTCEG score recompute
  25. 2026-10-05 21:44 UTCVendor advisory
  26. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  27. 2026-10-04 23:49 UTCEG score recompute
  28. 2026-10-04 23:49 UTCVendor advisory
  29. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-10-04 01:58 UTCEG score recompute
  31. 2026-10-04 01:58 UTCVendor advisory
  32. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  33. 2026-10-03 04:07 UTCEG score recompute
  34. 2026-10-03 04:07 UTCVendor advisory
  35. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  36. 2026-10-02 06:15 UTCEG score recompute
  37. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-10-01 08:24 UTCEG score recompute
  39. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-09-30 10:33 UTCEG score recompute
  41. 2026-09-29 12:36 UTCEG score recompute
  42. 2026-09-28 14:45 UTCEG score recompute
  43. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-09-28 11:12 UTCEG score recompute
  45. 2026-09-27 13:21 UTCEG score recompute
  46. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-09-25 17:37 UTCEG score recompute
  48. 2026-09-25 16:50 UTCEG score recompute
  49. 2026-09-25 16:24 UTCEG score recomputeFirst assessed: 6.0 MEDIUM
  50. 2026-09-25 16:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-66073?
CVE-2026-66073 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-66073 published?
The CVE record for CVE-2026-66073 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-66073 actively exploited?
CVE-2026-66073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66073?
CVE-2026-66073 has a CVSS v3 base score of 6.5 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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