CyberKit

Intel archive / Exploited vulnerabilities

VMware vCenter CVE-2026-59310: espionage, now ransomware

A critical vCenter flaw patched in July was first used for quiet espionage access; CISA now says ransomware gangs are exploiting it too.

Critical severity. Active. Moderate confidence. First reported 29 Jul 2026, last activity 15 Sep 2026. Briefing updated 27 Sep 2026.

AI-written summaries of public reporting, each checked against at least two sources from different publishers. Check the sources before you act. Last refreshed 2026-11-18 14:09 UTC. How this is made.

What is not settled: Summarized from coverage of CISA's warning; the Broadcom advisory and CISA KEV entry are the authorities for versions and dates.

In plain words

What happened

vCenter is the control panel for a company's virtual servers. A flaw in it lets an outsider run code on it without logging in.

Who is behind it

First a suspected state-backed group; since September, ransomware gangs as well.

What they want

Control of vCenter means control of every virtual machine, which is exactly what ransomware needs to encrypt a whole data center at once.

What they did

Hundreds of servers were compromised and backdoored after the July fix; CISA confirmed on 15 September that ransomware operators joined in.

Who is at risk

Organizations with an unpatched vCenter, especially any reachable from the internet.

What to do

  • Update vCenter to Broadcom's fixed version.
  • Treat vCenter as a crown jewel: no internet exposure, separate admin accounts.
The technical version, for hunting and patching

What happened

CVE-2026-59310 (CVSS 9.8): directory traversal in the vCenter Syslog server leading to unauthenticated RCE. Broadcom fixed it on 29 July 2026 (vCenter 9.1.0.0300, 9.0.2.0100, and 8.0 U3k/U2f tracks).

Who is behind it

A suspected APT deploying reverse-SSH tooling, then ransomware operators (per CISA, 15 September 2026).

What they want

Hypervisor-level control for persistence or mass encryption of VMs.

What they did

A DFIR firm reported 361+ compromised IPs across 47 countries with reverse SSH tools; CISA later confirmed ransomware use. Over 450 vCenter servers reportedly remained exposed with unknown patch status.

Who is at risk

Internet-exposed or flat-network vCenter; ESXi estates managed from it.

What to do

  • Patch to the fixed builds; if patching lagged, hunt for unexpected SSH keys, reverse-SSH processes and new local accounts on the appliance.
  • Place vCenter behind a management network or VPN; enforce MFA on admin access.
  • Check backups are immutable and not administrable from vCenter credentials.

Vulnerabilities

CVEs in this briefing
CVEProductCVSSCISA KEVFixed in
CVE-2026-59310VMware vCenter Server (Syslog service)9.8ListedBroadcom, 2026-07-29

Actors

  • Suspected APT (unattributed)
  • Ransomware operators (unnamed)

ATT&CK techniques

  • T1190: Exploit Public-Facing Application
  • T1021.004: Remote Services
  • T1486: Data Encrypted for Impact

Sectors: Multiple. Regions: Global.

Open next

Sources

Revision history

  • 2026-09-27: First published.

Newer: Device code phishing: a sign-in that hands over your account. Older: Cisco FMC auth bypass used by state and ransomware actors.