Broadcom’s VMware security advisory VMSA-2026-0006 was first published on 29 July 2026 and updated through 19 August 2026 as version 0006.2. It is rated Critical, with a CVSSv3 range of 2.7 to 9.8, and states that there are no workarounds. Two vCenter issues sit at the top of the matrix.
CVE-2026-59309 is an authentication-bypass vulnerability in the VMware Directory Service. Broadcom said a malicious actor with network access to vCenter may bypass authentication and gain unauthorised access, and scored it 9.8. CVE-2026-59310 is a directory-traversal vulnerability in the vCenter Syslog server. Broadcom said a malicious actor with network access may execute arbitrary code, also scored 9.8. Both were reported by Phil Brass and Matt South of Atredis Partners. Fixed versions listed in the response matrix include vCenter 9.1.0.0300, 9.0.2.0100, 8.0 U3k and 8.0 U2f, with Cloud Foundation and Telco SKUs pointed at matching patches or knowledge-base articles. vCenter 7.0 customers are told to contact Broadcom if they have extended support.
CISA added CVE-2026-59310 to its Known Exploited Vulnerabilities catalog on 18 August 2026, describing it as a Broadcom VMware vCenter path-traversal vulnerability with evidence of active exploitation. CISA did not, in that short alert, add CVE-2026-59309. Operators should still patch both vCenter bugs; Broadcom documented them together and said patches are cumulative.
The same advisory includes CVE-2026-47876, a critical out-of-bounds write in the VMXNET3 virtual adapter that requires local administrative privileges on a guest virtual machine, reported through Pwn2Own, and lower-severity issues CVE-2026-41703 and CVE-2026-41709. Those are not the KEV item. The exploited path CISA highlighted is the vCenter directory traversal.
vCenter is often reachable from too many internal networks, and sometimes from the internet for contractor convenience. Broadcom’s “network access” wording means the management plane must be treated as a high-value, tightly restricted service. After patching, administrators should look for unrecognised local users, unexpected syslog configuration and new processes on the appliance, because a code-execution bug may already have been used.
Home labs and small hosting companies are not exempt. A single exposed vCenter can give an attacker a path into every virtual machine the appliance manages. If you cannot patch the same day, disconnect vCenter from untrusted networks first. Broadcom stated plainly that no workaround exists, so network isolation is a temporary containment step, not a substitute for the fixed builds in the matrix.
What to do
• Snapshot configuration, then upgrade vCenter to a fixed version in Broadcom’s matrix. There is no workaround.
• Remove vCenter from the public internet. Allow only jump hosts or VPN administration.
• Patch ESXi for the VMXNET3 issue if guests could be used as a stepping stone.
• After upgrading, review vCenter SSO, syslog settings and appliance local accounts.
• Small organisations that still run nested labs or a single vCenter host should patch that host before any other virtualisation work this month.
Primary source: Broadcom VMSA-2026-0006, 29 July 2026, updated 19 August 2026; CISA KEV alert, 18 August 2026.
Sources
- Broadcom / VMware PSIRT — VMSA-2026-0006.1: VMware ESX, vCenter, Workstation, and Fusion updates address multiple vulnerabilities2026-09-24
- CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog2026-09-24
Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.
