VMware patches critical hypervisor escape in ESX, vCenter

A critical vulnerability in VMware’s ESX hypervisor may allow attackers with administrative access inside a guest virtual machine to execute arbitrary code on the underlying host. The flaw, tracked as CVE-2026-47876, resides in the VMXNET3 virtual network adapter and carries a CVSS score of 9.3. Broadcom released fixes on July 29, but applying them requires restarting ESX hosts, disrupting live workloads for multi-tenant providers and private-cloud operators alike.

What the advisory covers

Broadcom’s VMSA-2026-0006 advisory addresses five vulnerabilities, three of them rated critical. Alongside the ESX flaw, two vCenter Server vulnerabilities—CVE-2026-59309 (authentication bypass) and CVE-2026-59310 (directory traversal)—each score 9.8. The latter has been exploited in the wild since early August, with security firm QUIRSO identifying 361 compromised systems across 47 countries. Attackers used the flaw to install persistent backdoors via malicious cron jobs, though attribution remains unclear.

The ESX vulnerability specifically affects environments using the VMXNET3 adapter, which Broadcom recommends for performance in supported guest operating systems. Since many providers deploy this adapter by default in VM templates, the attack surface is broad for multi-tenant VPS and private-cloud offerings. Unlike the vCenter flaws, which require network access to the management interface, CVE-2026-47876 can be triggered by any customer with administrative privileges inside their own VM—a common feature in unmanaged services.

Operational impact

Patching the ESX flaw is operationally disruptive. Broadcom’s guidance classifies the advisory as an emergency change under ITIL, recommending rolling reboots using vMotion to evacuate workloads. For fleets without spare capacity or vMotion licensing, this may require scheduled downtime for customer VMs. ESX Live Patch can reduce disruption in supported environments, but the core requirement—restarting hosts—remains unchanged.

The vCenter vulnerabilities present a different risk profile. While their CVSS scores are higher, exploitation requires access to the management network. Properly segmented vCenter instances are harder to reach, but the authentication bypass (CVE-2026-59309) needs only network access to succeed. Security firm Defused Cyber reported a spike in scanning activity targeting vCenter’s SAML SSO flow, though it remains unclear whether these probes are linked to the ongoing exploitation of CVE-2026-59310.

Context and trends

This year has seen a surge in guest-to-host escapes across hypervisor platforms. Three similar vulnerabilities—ITscape, Januscape, and Zapscape—affected KVM earlier in 2026, with Januscape requiring only administrative access inside a guest VM. The pattern underscores a broader shift: tenant isolation in virtualized environments depends entirely on timely patching, and the operational cost of maintaining that isolation is rising. For VMware operators, this advisory arrives amid ongoing adjustments to Broadcom’s post-acquisition licensing model, adding another layer of complexity to fleet management.

No exploitation of CVE-2026-47876 has been reported, but the vCenter attacks demonstrate how quickly critical flaws can be weaponized. Providers must weigh the risk of delayed patching against the operational overhead of host restarts, particularly in environments where uptime SLAs are strict or spare capacity is limited.