Skip to content
major vulnerability· requires attention

VMware vCenter is widely deployed; an RCE in its management plane could disrupt enterprise infrastructure and is headline-worthy.

Infrastructure

CVE-2026-59310

9.8
Critical
KEV · Exploited in wildEPSS 46%Patch availableJul 30, 2026

Directory traversal in VMware vCenter Syslog enables remote code execution.

common questions

Is CVE-2026-59310 being exploited?

Yes. CVE-2026-59310 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-59310?

CVE-2026-59310 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-59310?

Yes. A fix has been recorded for CVE-2026-59310. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-59310 affect?

CVE-2026-59310 affects VMware vCenter Server (Syslog service). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59310?

Apply vendor patch when released; restrict network access to vCenter and block Syslog exposure.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
VMware vCenter Server (Syslog service)
impact

Remote code execution via directory traversal in vCenter Syslog; attacker with network access can execute arbitrary code and fully compromise management.

action required

Immediate action required

affected versions
VMware Cloud Foundation
  • affected9.1.x.x
  • affected9.0.x.x
  • affected5.x
VMware Telco Cloud Infrastructure
  • affected3.0
VMware Telco Cloud Platform
  • affected5.1.x
  • affected5.0.x
  • affected4.x
  • affected3.0
VMware vCenter
  • affected>= 9.1.x.x and < 9.1.0.0300
  • affected>= 9.0.x.x and < 9.0.2.0100
  • affected>= 8.0 and < 8.0 U3k
VMware vSphere Foundation
  • affected9.1.x.x
  • affected9.0.x.x

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free