On 29 July 2026, Broadcom published security advisory VMSA-2026-0006 addressing five vulnerabilities across VMware ESXi, vCenter Server, Workstation, and Fusion. Three of these flaws carry critical severity ratings with CVSS scores up to 9.8, and they strike at the virtualisation management plane that underpins most modern data centres. There are no workarounds — only vendor-supplied patches — and one vulnerability enables an attacker to break out of a virtual machine and execute code on the underlying ESXi host. For organisations running vSphere, this is work for the current maintenance window, not next month's.
The advisory covers two unauthenticated remote vulnerabilities in vCenter Server and a VM escape in ESXi's VMXNET3 virtual network adapter. Broadcom reports no evidence of in-the-wild exploitation as of the publication date, but the absence of mitigations and the history of rapid weaponisation of vSphere flaws mean the window for safe patching is narrow. The updates are classified as emergency changes under ITIL methodologies, and Broadcom's supplemental FAQ warns of a "back in time" compatibility issue that temporarily blocks upgrades to VMware Cloud Foundation 9.x when applying the vSphere 8.0 and 9.0 patches.
What's New / Specs
VMSA-2026-0006 bundles five distinct vulnerabilities. The three critical issues present the highest risk:
- CVE-2026-59309 (CVSS 9.8) — Authentication bypass in the VMware Directory Service of vCenter Server. An unauthenticated attacker with network access to vCenter can bypass authentication and gain unauthorised access to the management plane. No credentials are required.
- CVE-2026-59310 (CVSS 9.8) — Directory traversal in the vCenter Syslog server. A remote, unauthenticated attacker with network access can read or write arbitrary files, ultimately achieving remote code execution on the vCenter system.
- CVE-2026-47876 (CVSS 9.3) — Out-of-bounds write in the VMXNET3 virtual network adapter on ESXi. An attacker with local administrative privileges inside a virtual machine using the VMXNET3 adapter can execute code on the ESXi host, constituting a virtual machine escape. Virtual machines using other virtual network adapters (such as E1000E) are not affected by this specific flaw.
Two additional vulnerabilities round out the advisory:
- CVE-2026-41703 — Out-of-bounds read in ESXi, Workstation, and Fusion (CVSS 7.6 on ESXi, rated Important; CVSS 2.7 on Workstation and Fusion, rated Low, limited to information disclosure). An attacker with VM deployment privileges could trigger information disclosure or, more likely, a denial-of-service condition on the host process.
- CVE-2026-41709 (CVSS 2.7, Low) — Insufficient logging in ESXi. A malicious administrator could perform certain operations without those actions being logged, complicating forensic analysis.
Fixed builds are available across the product portfolio. For vCenter Server, the patched versions are 9.1.0.0300, 9.0.2.0100, and 8.0 Update 3k. ESXi receives fixes in versions 9.1.0.0200, 9.0.2.0100, and 8.0 Update 3k (with build numbers ESXi-9.1.0.0200-25557999, ESXi-9.0.2.0100-25595025, and ESXi80U3k-25595708 respectively). VMware Cloud Foundation and vSphere Foundation 9.1.x and 9.0.x map to the corresponding vCenter and ESXi releases. VMware Cloud Foundation 5.x and the Telco Cloud Platform and Telco Cloud Infrastructure products have separate patching instructions referenced in the advisory (KB449886 and async patching guide KB88287). Workstation and Fusion users on version 25H2 must upgrade to 26H1 to address CVE-2026-41703.
Broadcom's advisory notes that patches are cumulative. For the 9.1 branch, CVE-2026-59309 was first addressed in 9.1.0.0200, but 9.1.0.0300 is the most recent version available and includes all fixes. The company explicitly states there are no workarounds for any of the five vulnerabilities. Switching virtual machines away from the VMXNET3 adapter is not recommended because other virtual network adapters have also contained security flaws and may reduce performance.
Why It Matters
vCenter Server is the central management plane for vSphere environments. It controls ESXi hosts, virtual machines, permissions, templates, and operational workflows across the entire platform. Compromising vCenter does not merely affect a single server — it grants the attacker the keys to every host and workload managed by that vCenter instance. An unauthenticated authentication bypass (CVE-2026-59309) against this component is therefore as severe as its CVSS 9.8 rating implies: network access to the management interface alone is sufficient for initial compromise. From there, an attacker can modify permissions, deploy malicious workloads, clone or exfiltrate virtual machines, and move laterally across the virtualised estate.
The VM escape vulnerability (CVE-2026-47876) attacks virtualisation's core isolation promise. While it requires local administrator privileges inside a guest VM — a higher bar than the vCenter flaws — this condition is routinely met in multi-stage intrusions where a workload is compromised first and the attacker then escalates toward the infrastructure. A successful escape from a VMXNET3-equipped VM yields code execution on the ESXi host, exposing every other VM sharing that host. This pattern is not unique to VMware; similar escape vulnerabilities have appeared in KVM and other hypervisors, reinforcing that hypervisor isolation is a security barrier, not an unbreakable boundary.
The same urgency shows up in compliance terms: operators under ICT resilience rules (for example NIS2 and similar frameworks) are expected to handle known critical flaws promptly — an unpatched vCenter with a CVSS 9.8 exposure is hard to defend after an incident. Concentration risk — where many critical services sit on one virtualisation platform — turns a management-plane flaw into a systemic risk for the organisation.
Broadcom's FAQ highlights operational considerations for patching. Updating vCenter temporarily interrupts access to the vSphere Client and other management interfaces, though running VMs and containers continue operating. ESXi updates require a host reboot; Broadcom recommends using vMotion to migrate VMs to other hosts for a rolling cluster update, powering down VMs that cannot be migrated. Supported environments may use ESXi Live Patch to reduce disruption, though vCenter updates are not eligible for Quick Patch. The "back in time" restriction — where vSphere 8.0 and 9.0 patches carry newer build numbers than the target VCF 9.x upgrade path — blocks VCF 9.x upgrades until later releases restore compatibility.
Our Take
VMSA-2026-0006 is not a routine patch cycle. It combines an unauthenticated authentication bypass and remote code execution on the brain of the virtualisation platform with a VM escape on the hypervisor itself. The lack of public exploitation today is a window, not a guarantee; vSphere vulnerabilities have a documented history of moving from patch release to mass exploitation within days or weeks, frequently leveraged by ransomware operators who encrypt ESXi datastores directly. The absence of any workaround sharpens the urgency: either the patch is applied or the system remains exposed.
Prioritisation should be driven by exposure and criticality, not CVSS alone. Internet-facing or broadly reachable vCenter instances must be patched first, followed by hosts carrying critical workloads. Network segmentation of the management plane — restricting vCenter and ESXi interfaces to a dedicated management network with allow-list access, bastion hosts or VPN with MFA, and no internet exposure — remains the single most effective architectural control. However, segmentation does not mitigate the VM escape once an attacker has a foothold inside a guest VM, which is why patching the ESXi host is equally non-negotiable.
Telemetry improvements are essential. Monitor for anomalous vCenter logins, unexpected account creation, permission changes, and unusual file writes on the Syslog service. Remember that CVE-2026-41709 allows an administrator to act without leaving a log entry in vCenter's own logs; do not rely solely on those logs for detection. Document patch dates, versions, and assets covered as evidence of diligence for auditors and compliance reviews. If indicators of compromise are found, trigger incident response before declaring the environment clean.
FAQ
Which products and versions are affected by VMSA-2026-0006?
The advisory covers VMware ESXi, vCenter Server, Workstation, Fusion, VMware Cloud Foundation, vSphere Foundation, Telco Cloud Platform, and Telco Cloud Infrastructure. Specific affected version ranges are detailed in Broadcom's response matrix; generally, any version prior to the fixed releases listed in the advisory should be considered vulnerable.
Are there any workarounds for the critical vulnerabilities?
No. Broadcom explicitly states there are no workarounds for CVE-2026-59309, CVE-2026-59310, or CVE-2026-47876. The only remediation is applying the vendor-supplied patches. Switching VMs away from the VMXNET3 adapter is not advised because other adapters have also had security flaws and may reduce performance.
Does the VM escape (CVE-2026-47876) affect all virtual network adapters?
No. The vulnerability is specific to the VMXNET3 virtual network adapter. Virtual machines using other adapters such as E1000E are not affected by this particular flaw, though Broadcom cautions that other adapters have had their own security issues historically.
What is the "back in time" restriction mentioned in Broadcom's FAQ?
Applying the vSphere 8.0 and 9.0 patches from this advisory updates the product branch to a build number newer than the target of a planned VMware Cloud Foundation 9.x upgrade. This causes a "back in time" error that blocks the VCF 9.x upgrade. Broadcom states upgrade compatibility will be restored in later releases.
Has any exploitation been observed in the wild?
As of the advisory date (29 July 2026), Broadcom reports no evidence of in-the-wild exploitation or active scanning for these vulnerabilities. However, vCenter Server has appeared on CISA's Known Exploited Vulnerabilities (KEV) list ten times previously for other flaws, indicating that attackers actively target critical issues in this product.
