Broadcom released patches for five VMware vulnerabilities, three of them rated critical. The most severe, CVE-2026-47876, is an out-of-bounds write in ESXi’s VMXNET3 virtual network adapter that enables a VM escape: an attacker with local administrative privileges on a virtual machine can exploit the flaw to execute arbitrary code on the host hypervisor. Two additional critical vulnerabilities affect vCenter Server. Broadcom reports no confirmed in-the-wild exploitation of any of the five flaws as of July 29.
CVE-2026-47876: An ESXi VM Escape via the VMXNET3 Network Adapter
CVE-2026-47876 is a critical-severity out-of-bounds write vulnerability in ESXi’s implementation of the VMXNET3 virtual network adapter. A threat actor who holds local administrative privileges on a guest VM can exploit the flaw to write data outside the intended memory bounds of the adapter’s buffer, gaining execution control at the hypervisor level. That transitions the attacker from operating inside the guest virtual machine’s boundaries to operating on the physical host that runs all VMs on that server.
The VMXNET3 adapter is VMware’s high-performance virtual network interface, commonly used in enterprise ESXi deployments for performance-sensitive workloads. It is not an obscure or non-default component — it is a standard part of VMware’s virtual hardware configuration in many production environments.
What VM Escape Means for Multi-Tenant and Shared Virtualization Environments
When an attacker escapes from a virtual machine to the ESXi host, they exit the isolation boundary that makes virtualization a useful security mechanism. From the host, the attacker has access to the memory of every other VM running on the same physical server, the ability to power VMs on or off, access to the hypervisor’s file system and stored VM disk images, and control over the virtual networking infrastructure that connects all hosted VMs.
In enterprise environments, this typically means an attacker who compromises one tenant’s virtual machine — through a vulnerability in a hosted application, a misconfigured service, or a compromised credential — can potentially pivot to access VMs belonging to other tenants, business units, or security zones if they are colocated on the same hypervisor. The security architecture that places different workloads in separate VMs assumes the VM boundary holds; CVE-2026-47876 shows it does not.
CVE-2026-59309 and CVE-2026-59310: Two Critical vCenter Server Vulnerabilities
The July 29 patch batch also addresses two critical vulnerabilities in vCenter Server, the centralized management platform for VMware virtualized environments.
CVE-2026-59309 is an authentication bypass in vCenter Server that enables unauthorized access to the targeted system. CVE-2026-59310 allows an attacker with network access to vCenter Server to execute arbitrary code.
The Combined Risk of vCenter and Hypervisor Vulnerabilities in the Same Patch Cycle
vCenter Server occupies a uniquely high-value position in VMware environments: it is the single pane of glass through which administrators manage every ESXi host, virtual machine, storage system, and network configuration across the entire virtualized infrastructure. A compromised vCenter server gives an attacker administrative control over all managed ESXi hosts — which means the authentication bypass in CVE-2026-59309 could serve as a path to ESXi hypervisor control without requiring a guest VM as a starting point.
Patching both the vCenter authentication bypass and the ESXi VM escape in the same cycle is critical. An attacker who can bypass vCenter authentication could potentially chain that access with CVE-2026-47876, or with CVE-2026-59310’s code execution capability, to achieve full hypervisor compromise through a path that does not require any guest VM foothold at all.
The Two Remaining Vulnerabilities: High and Low Severity
CVE-2026-41703, rated High, affects ESXi, Workstation, and Fusion and allows an attacker with VM deployment permissions to obtain information or cause a denial-of-service condition. CVE-2026-41709, rated Low, affects ESXi and allows an admin-privileged attacker to conduct activities without generating log entries — a capability that enables operational security for an attacker already inside the environment.
Patch Priority Given VMware’s Active Exploitation History
Broadcom states that none of the five vulnerabilities in this batch are known to be exploited in the wild. That status has changed rapidly for past VMware critical patches: multiple previous ESXi and vCenter critical flaws have moved from no-known-exploitation to active attack within days to weeks of patch publication. Organizations should treat the VMXNET3 VM escape and both critical vCenter flaws as emergency patches rather than routine updates, applying them on an expedited schedule before exploitation activity develops. Broadcom has released patches for all affected products, covering ESXi, vCenter Server, Workstation, and Fusion.
