CVE-2026-59310

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-08-18), indicating real-world exploitation has been confirmed by US federal agencies. It is also listed on ENISA's EU Known Exploited Vulnerabilities catalogue (Source: ENISA EUVD). The CNA's CVSS baseline 9.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, the CNA's CVSS, EPSS, ENISA's EU Known Exploited Vulnerabilities catalogue, GitHub Security Advisory
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2026-51097 (ENISA EUVD) · GHSA-v2gp-49gj-2c9f (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedENISA EU KEV: Listed (Source: ENISA EUVD)EPSS PROB: 2.6%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VMware by Broadcom) lists VMware vCenter versions before 9.1.0.0300 and before 9.0.2.0100 as affected. No release containing a fix is confirmed on record.

VMware vCenter contains a directory traversal vulnerability in the Syslog server. A malicious actor with network access to vCenter may exploit this issue to execute arbitrary code.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high.
EPSS PROB
2.6%
EPSS %ILE
85th
KEV
⚠ Exploited

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

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

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and ENISA EU KEV (Source: ENISA EUVD) and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

ENISA EU KEV: listed August 10, 2026, reported by ENISA.

Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. How a listing moves the EG score

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-59310

Published

July 30, 2026

Last Modified

September 12, 2026

Advisory Details (2)

Auto-updated Oct 31, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet.
Web page

Support Content Notification - Support Portal - Broadcom support portal

https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-59310

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 139× 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.

Showing the most recent 100 of 704 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 604 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 01:04 UTCEG score recompute
  2. 2026-11-02 01:04 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-01 16:35 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  4. 2026-10-31 23:26 UTCEG score recompute
  5. 2026-10-31 23:26 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  7. 2026-10-30 21:50 UTCEG score recompute
  8. 2026-10-30 21:50 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  10. 2026-10-29 20:14 UTCEG score recompute
  11. 2026-10-29 20:14 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-29 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  13. 2026-10-28 18:38 UTCEG score recompute
  14. 2026-10-28 18:37 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-28 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  16. 2026-10-27 17:00 UTCEG score recompute
  17. 2026-10-27 16:59 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  19. 2026-10-26 16:31 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  20. 2026-10-26 15:23 UTCEG score recompute
  21. 2026-10-26 15:23 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-25 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  23. 2026-10-25 13:47 UTCEG score recompute
  24. 2026-10-25 13:47 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-25 13:46 UTCENISA EU KEV listingEUVD-2026-51097 · listed August 10, 2026 · reported by ENISA · Source: ENISA EUVD
Show 75 more
  1. 2026-10-25 05:22 UTCEG score recompute
  2. 2026-10-25 05:22 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-24 16:33 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  4. 2026-10-24 03:45 UTCEG score recompute
  5. 2026-10-24 03:45 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  7. 2026-10-23 02:09 UTCEG score recompute
  8. 2026-10-23 02:09 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-22 16:34 UTCEPSS rescoreEPSS 2.6% · 85th percentile
  10. 2026-10-22 00:33 UTCEG score recompute
  11. 2026-10-22 00:32 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  13. 2026-10-20 22:53 UTCEG score recompute
  14. 2026-10-20 22:53 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  16. 2026-10-19 21:17 UTCEG score recompute
  17. 2026-10-19 21:17 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  19. 2026-10-18 19:41 UTCEG score recompute
  20. 2026-10-18 19:41 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-18 16:32 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  22. 2026-10-18 03:27 UTCEG score recompute
  23. 2026-10-17 18:03 UTCEG score recompute
  24. 2026-10-17 18:03 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  26. 2026-10-16 16:43 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  27. 2026-10-16 16:26 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-15 21:23 UTCEG score recompute
  29. 2026-10-15 21:23 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  31. 2026-10-14 19:45 UTCEG score recompute
  32. 2026-10-14 19:44 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-14 16:33 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  34. 2026-10-13 18:08 UTCEG score recompute
  35. 2026-10-13 18:07 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  37. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  38. 2026-10-12 16:28 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-12 15:52 UTCEG score recompute
  40. 2026-10-12 06:29 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-12 02:37 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-11 22:47 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-11 19:36 UTCEG score recompute
  44. 2026-10-11 18:56 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-11 16:51 UTCEG score recompute
  46. 2026-10-11 15:05 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-11 14:14 UTCEG score recompute
  48. 2026-10-11 13:49 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  49. 2026-10-11 11:14 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-11 07:22 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-11 03:30 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-10 23:40 UTCEG score recompute
  53. 2026-10-10 23:40 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  55. 2026-10-10 19:49 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-10 15:55 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-10 12:04 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-10 08:14 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-10 04:23 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-10 00:33 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-09 20:43 UTCEG score recompute
  62. 2026-10-09 20:42 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  64. 2026-10-09 16:52 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-09 13:02 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-09 09:10 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-09 05:19 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-09 01:29 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-08 21:39 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-08 17:49 UTCEG score recompute
  71. 2026-10-08 17:49 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-08 17:13 UTCEPSS rescoreEPSS 2.6% · 84th percentile
  73. 2026-10-08 13:58 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-08 10:07 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-08 06:17 UTCGHSA enrichmentGHSA-v2gp-49gj-2c9f · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (4 GitHub PoCs). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • GitHub PoCchu0119/vc-strike
    Published Oct 1, 2026

    VC-Strike — VMware vCenter CVE-2026-59310 (unauth root RCE) & CVE-2026-59309 (SRP auth bypass) authorized pentest suite. GUI+CLI, multi-session C2, stdlib-only. 授权测试专用

    Open source ↗
  • GitHub PoCChinaRan0/CVE-2026-59310-POC
    Published Sep 25, 2026

    CVE-2026-59310-POC 仅用于自测,请勿用于攻击

    Open source ↗
  • GitHub PoCzgsfsec/CVE-2026-59310-POC
    Published Sep 25, 2026

    CVE-2026-59310-POC 仅用于自测,请勿用于攻击

    Open source ↗
  • GitHub PoCBiuTrap/CVE-2026-59310
    Published Aug 17, 2026

    CVE-2026-59310 PoC

    Open source ↗

Frequently asked(6)

What is CVE-2026-59310?
CVE-2026-59310 is a critical-severity vulnerability; its CVE record was published on July 30, 2026. VMware vCenter contains a directory traversal vulnerability in the Syslog server. A malicious actor with network access to vCenter may exploit this issue to execute arbitrary code.
When was CVE-2026-59310 made public?
CVE-2026-59310 was made public on July 29, 2026: that is the date its CVE record's CNA, VMware by Broadcom, gives for when the vulnerability was made public. The CVE record itself was published on July 30, 2026. EchelonGraph's copy of the record carries a last-modified date of September 12, 2026; the record at its source may have been updated since.
Is CVE-2026-59310 actively exploited?
Yes. CISA added CVE-2026-59310 to the Known Exploited Vulnerabilities catalog on August 18, 2026, affecting Broadcom VMware vCenter. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation. ENISA's EU Known Exploited Vulnerabilities catalogue lists CVE-2026-59310 (added August 10, 2026, reported by ENISA): ENISA records its exploitation in the wild. Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement.
What is the CVSS score of CVE-2026-59310?
CVE-2026-59310 has a CVSS base score of 9.8 (the CNA's own assessment, by vmware; NVD's own analysis pending).
Which products are affected by CVE-2026-59310?
CVE-2026-59310 affects Broadcom VMware vCenter.
How do I remediate CVE-2026-59310?
No fix for CVE-2026-59310 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VMware by Broadcom) lists VMware vCenter versions before 9.1.0.0300 and before 9.0.2.0100 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-59310 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59310?

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