Summary
This advisory updates and extends GARNET-CSIRT-2026-003, which covered exploitation of CVE-2026-59310 in VMware vCenter. Since then the threat around Broadcom advisory VMSA-2026-0006 has grown in three ways:
- CVE-2026-59310 (vCenter Syslog directory traversal, CVSS 9.8) is now flagged by CISA as known to be used in ransomware campaigns, and public proof-of-concept code has been reported.
- CVE-2026-41709 (ESX insufficient logging, rated only CVSS 2.7) was exploited as a zero-day by a China-nexus espionage group to hide administrator activity on ESX hosts. CISA added it to the Known Exploited Vulnerabilities catalog on 28 October 2026.
- CVE-2026-59309 (vCenter authentication bypass, CVSS 9.8), fixed in the same release, has been probed in the wild since August.
VMSA-2026-0006 also fixes CVE-2026-47876 (CVSS 9.3), an ESX flaw that lets an administrator inside a virtual machine execute code on the host. Broadcom revised the advisory on 19 August 2026 to add guidance for vCenter and ESX 7.0. None of the vulnerabilities has a workaround.
Impact
Exploitability signals: CVSS 9.8 for both vCenter flaws · CVE-2026-59310 on CISA KEV with known ransomware use · CVE-2026-41709 on CISA KEV as an exploited zero-day · public proof-of-concept reported for CVE-2026-59310 · no workarounds.
vCenter manages every ESX host and virtual machine in a vSphere environment, and ESX hosts run the workloads themselves. Ransomware operators who reach this layer encrypt virtual machine disk files directly on the hosts, taking down every server in the cluster at once, including backups that are stored on the same platform.
CVE-2026-41709 shows why low CVSS scores can mislead. It grants no access by itself, but attackers who already had a foothold used it so that their ESX administrator commands never appeared in audit logs. In the reported campaign, attributed to the group tracked as Warp Panda (also known as UNC5221, Clay Typhoon and VerdantBamboo), the intruders entered through an exposed VPN or remote access appliance, planted the BRICKSTORM backdoor on virtualization hosts, and then used stolen session cookies to reach Microsoft 365 mailboxes. Institutions that rely on ESX logs to rule out compromise should not assume those logs are complete.
Affected systems
Fixed releases from VMSA-2026-0006.2:
- vCenter 9.1 fixed in 9.1.0.0300 (CVE-2026-59309, CVE-2026-59310)
- vCenter 9.0 fixed in 9.0.2.0100 (CVE-2026-59309, CVE-2026-59310)
- vCenter 8.0 fixed in 8.0 U3k or 8.0 U2f (CVE-2026-59309, CVE-2026-59310)
- vCenter 7.0 patches are available only to customers with a Broadcom extended support contract
- ESX 9.1 fixed in ESXi-9.1.0.0200-25557999 (CVE-2026-47876) and ESXi-9.1.0.0-25370933 (CVE-2026-41703, CVE-2026-41709)
- ESX 9.0 fixed in ESXi-9.0.2.0100-25595025 (all ESX CVEs)
- ESX 8.0 fixed in ESXi80U3k-25595708 on the U3 line, which includes the earlier U3i and U3j fixes for CVE-2026-41703 and CVE-2026-41709. On the U2 line, ESXi80U2f-25626445 fixes CVE-2026-47876.
- ESX 7.0 patches for CVE-2026-47876 are available only with extended support
- VMware Cloud Foundation 5.x fixed through the async patch in Broadcom KB88287 and VCF 5.2.4
- VMware Workstation and Fusion 25H2 fixed in 26H1 (CVE-2026-41703, low severity)
vSphere 7.0 reached end of general support in October 2025. Institutions still running it without an extended support contract cannot obtain these fixes and should plan an upgrade to 8.0 as a priority.
Action
-
Patch vCenter and every ESX host now. Apply the fixed release for your version from the list above. Patch vCenter first, then the ESX hosts. If you patched vCenter for GARNET-CSIRT-2026-003 but have not patched ESX, you are still exposed to CVE-2026-47876 and CVE-2026-41709.
-
Take vCenter and ESX management off the internet. The vCenter web interface, API and Syslog service, and ESX management interfaces, should be reachable only from a dedicated management network or administrative VPN. Exposed vCenter servers were the entry point for the CVE-2026-59310 campaign.
-
Check whether you were already compromised. If any vCenter was internet-reachable and unpatched at any point since 3 August 2026, treat it as potentially compromised and follow the hunting guidance in GARNET-CSIRT-2026-003, including the search for the reverse_ssh tool. GARNET CSIRT continues to notify members whose addresses appear in the Shadowserver victim report for this campaign.
-
Do not rely on ESX logs alone. Because CVE-2026-41709 lets attackers hide administrator activity, look for other evidence on ESX hosts: unexpected files, processes or services, unknown local accounts, unexplained changes to virtual machines, and outbound connections to unfamiliar addresses. Check virtualization hosts and vCenter for the BRICKSTORM backdoor using published vendor detection content.
-
Audit your edge devices. The reported intrusions began at exposed VPN and remote access appliances. Confirm those devices are fully patched, review their logs for unusual logins, and make sure their management interfaces are not internet-facing.
-
Protect your backups from the virtualization layer. Keep at least one backup copy offline or on infrastructure that vCenter and ESX credentials cannot reach, and test that it restores. This is the main safeguard against hypervisor-level ransomware.
-
Review cloud identity for signs of follow-on access. Where staff use Microsoft 365, review recently registered MFA devices and revoke active sessions for administrator and other sensitive accounts if compromise is suspected anywhere in the environment.
-
Report suspected compromise. Institutions that find signs of intrusion on vCenter, ESX or edge appliances should report the incident so we can correlate activity across the constituency.
This advisory is published with a detached PGP signature against the CSIRT key. Confirm it is genuine and unmodified before acting:
Downloads: source .md · signature .md.asc · public key. Check the fingerprint (684C7B7DA77E4F1B68AED3ECE84B541C6184CC6F) on the PGP page — if gpg reports a “Good signature” from that key, this advisory is authentic.
Think a system in the community is affected or compromised?Report an incident