Broadcom has released VMSA-2026-0006, a critical security advisory addressing five vulnerabilities across VMware vCenter Server, ESX/ESXi, Workstation, Fusion, VMware Cloud Foundation (VCF), and VMware vSphere Foundation (VVF). Three of the flaws are rated Critical, including two remotely exploitable vulnerabilities affecting vCenter and a virtual machine escape vulnerability impacting ESX hosts through the VMXNET3 virtual network adapter.
For enterprise environments, the advisory is significant because it affects both the virtualization management plane and the hypervisor itself. A successful attack against vCenter can compromise the administrative control point for an organization’s virtual infrastructure, while exploitation of the VMXNET3 flaw could allow an attacker who has already compromised a virtual machine to break isolation and execute code on the underlying ESX host. Broadcom has stated that it has no evidence of active exploitation in the wild at the time of publication, but given the severity and central role of VMware infrastructure in enterprise environments, administrators should prioritize patching.
Technical Overview
Virtualized infrastructure relies on several security boundaries. vCenter acts as the centralized management platform responsible for provisioning virtual machines, managing clusters, controlling permissions, and orchestrating storage and networking. ESX/ESXi serves as the hypervisor that isolates guest operating systems from one another and from the physical host.
Because of this architecture, vulnerabilities affecting either component can have disproportionate consequences. A compromise of vCenter potentially grants administrative control over the entire virtual environment, while a hypervisor escape breaks one of virtualization’s core security assumptions by allowing code running inside a guest VM to interact with the host operating system.
Broadcom’s latest advisory spans vulnerabilities across both layers.
Vulnerability Summary
| CVE | Component | Severity | CVSS | Impact |
|---|---|---|---|---|
| CVE-2026-59309 | VMware vCenter Directory Service | Critical | 9.8 | Authentication bypass |
| CVE-2026-59310 | VMware vCenter Syslog Server | Critical | 9.8 | Directory traversal leading to arbitrary code execution |
| CVE-2026-47876 | VMware ESX VMXNET3 | Critical | 9.3 | VM escape and host code execution |
| CVE-2026-41703 | ESX, Workstation, Fusion | Important | 7.6 (ESX) | Information disclosure and possible denial of service |
| CVE-2026-41709 | VMware ESX | Low | 2.7 | Insufficient logging of administrative operations |
CVE-2026-59309: Authentication Bypass in VMware vCenter
The most severe issue tracked as CVE-2026-59309 affects the VMware Directory Service within vCenter Server and carries a CVSS score of 9.8.
According to Broadcom, an attacker with network access to vCenter can exploit the flaw to bypass authentication and gain unauthorized access to the management platform. No valid credentials are required once the vulnerability is successfully exploited. (reddit.com)
Although Broadcom has not publicly disclosed the underlying implementation details, the practical impact is straightforward. vCenter is responsible for managing ESX hosts, virtual machines, clusters, distributed networking, permissions, snapshots, templates, and storage policies. Unauthorized access to this management plane could enable attackers to manipulate virtual infrastructure, deploy malicious virtual machines, alter configurations, or pivot deeper into enterprise environments.
Because authentication represents the first security boundary protecting the management plane, bypass vulnerabilities are considered among the most dangerous classes of flaws affecting enterprise infrastructure.
CVE-2026-59310: Directory Traversal Leading to Remote Code Execution
The second critical vulnerability, CVE-2026-59310, also receives a CVSS score of 9.8 and affects the vCenter Syslog Server.
Broadcom describes the issue as a directory traversal vulnerability that allows a remote attacker with network access to execute arbitrary code on the vCenter Server.
Directory traversal vulnerabilities occur when software improperly validates file paths supplied by a user. Instead of remaining confined to expected directories, specially crafted path sequences may allow access to unintended locations on the filesystem.
In this case, Broadcom has confirmed that exploitation can ultimately result in arbitrary code execution rather than merely unauthorized file access. While the vendor has intentionally withheld technical details to reduce the risk of weaponization before patch adoption, successful exploitation could effectively hand control of the vCenter appliance to an attacker.
Since vCenter often maintains privileged communication with multiple ESX hosts, a compromise of the management server can become a launching point for broader attacks against the virtualization environment.
CVE-2026-47876: VM Escape Through VMXNET3
Perhaps the most technically significant issue in the advisory is CVE-2026-47876, an out-of-bounds write vulnerability affecting the VMXNET3 virtual network adapter.
VMXNET3 is VMware’s high-performance paravirtualized network interface designed to reduce virtualization overhead while improving network throughput inside guest operating systems.
Broadcom states that an attacker who already possesses local administrative privileges inside a virtual machine using VMXNET3 can trigger an out-of-bounds write that enables execution of code on the underlying ESX host. Broadcom explicitly classifies this issue as a virtual machine escape.
Virtual machine escapes are among the most serious vulnerabilities affecting hypervisors because they violate the isolation boundary separating guest workloads from the host. Under normal operation, a compromised guest operating system should remain confined to its own virtual environment. A successful escape allows malicious code to cross that boundary and interact directly with the hypervisor.
Unlike the vCenter vulnerabilities, exploitation requires prior compromise of a guest VM together with administrative privileges inside that VM. Nevertheless, organizations operating multi-tenant environments or hosting workloads from different trust levels should treat this vulnerability as high priority because a successful escape may expose neighboring virtual machines running on the same physical host.
Additional Vulnerabilities
Broadcom also addressed two lower-severity vulnerabilities.
CVE-2026-41703 is an out-of-bounds read affecting VMware ESX, Workstation, and Fusion. On ESX, exploitation may result in information disclosure or a denial-of-service condition. On Workstation and Fusion, Broadcom states that the impact is limited to information disclosure. Exploitation on ESX requires VM deployment privileges.
CVE-2026-41709 is an insufficient logging vulnerability affecting VMware ESX. Rather than enabling system compromise, it allows certain administrative operations to occur without being properly recorded in audit logs. While assigned a low CVSS score of 2.7, missing audit records can complicate forensic investigations and incident response after a security event.
Affected Versions and Security Updates
Broadcom has released updates across supported VMware product lines.
vCenter Server
| Product | Fixed Version |
|---|---|
| VMware Cloud Foundation / vSphere Foundation 9.1.x | 9.1.0.0300 |
| VMware Cloud Foundation / vSphere Foundation 9.0.x | 9.0.2.0100 |
| VMware vCenter Server 8.0 | 8.0 U3k |
| VMware Cloud Foundation 5.x | Async patch aligned with vCenter 8.0 U3k |
ESX Hypervisor
| Vulnerability | Fixed Builds |
|---|---|
| CVE-2026-47876 | ESXi-9.1.0.0200-25557999, ESXi-9.0.2.0100-25595025, ESXi80U3k-25595708 |
| CVE-2026-41703 | ESXi-9.1.0.0-25370933, ESXi-9.0.2.0100-25595025, ESXi80U3i-25205845 |
| CVE-2026-41709 | ESXi-9.1.0.0-25370933, ESXi-9.0.2.0100-25595025, ESXi80U3j-25429389 |
Desktop Hypervisors
| Product | Fixed Version |
|---|---|
| VMware Workstation | 26H1 |
| VMware Fusion | 26H1 |
Enterprise Impact
Organizations frequently place vCenter on internal management networks rather than exposing it directly to the Internet. While this reduces exposure to external attackers, it does not eliminate risk. An adversary who gains an initial foothold through phishing, compromised VPN credentials, remote access malware, or another internal breach could target vulnerable vCenter servers to expand privileges within the virtual infrastructure.
Likewise, the VM escape vulnerability should be evaluated in environments where workloads from different trust levels share the same physical host. Cloud providers, managed service providers, research environments, and enterprise virtualization clusters benefit from strong guest isolation. Any vulnerability capable of breaching that boundary deserves immediate attention, even when exploitation requires administrative control of a guest operating system.
Broadcom has not published workarounds for the critical vulnerabilities, making software updates the only recommended remediation.
Recommendations
Organizations should prioritize updating all internet-accessible and internally accessible vCenter instances before addressing the remaining affected products. ESX hosts running virtual machines that use the VMXNET3 adapter should also be patched as soon as operationally feasible. After updates are complete, administrators should review authentication logs, administrative activity, and configuration changes for signs of unauthorized access, particularly if patching was delayed.
Although there are currently no reports of in-the-wild exploitation, history shows that high-severity VMware vulnerabilities often receive significant attention from both security researchers and threat actors shortly after patches become available. Applying Broadcom’s updates promptly remains the most effective defense against these flaws.
