A Critical VMware Bug Can Let Code Escape the VM and Reach the Host
- The Mess: Broadcom has disclosed critical vulnerabilities affecting VMware Workstation and Fusion. CVE-2026-59346, rated CVSS 9.3, can allow code execution on the host from a vulnerable virtual machine, while CVE-2026-59347 exposes another host-side attack path through a memory corruption flaw.
- The Damage: A virtual machine is supposed to isolate untrusted workloads from the host. If an attacker can cross that boundary, the compromise stops being contained inside the VM.
- The Fix: Update VMware Workstation and Fusion immediately to the patched versions provided by Broadcom and treat untrusted virtual machines as potentially hostile until the affected software is fixed.
Virtual machines exist for a reason.
Run something dangerous inside the guest.
Keep the host safe.
Broadcom has now disclosed vulnerabilities that can attack exactly that security boundary.
The most serious issue is CVE-2026-59346, a critical integer overflow vulnerability affecting the VMXNET3 virtual network adapter.
The flaw carries a CVSS score of 9.3.
According to the security advisory, an attacker with the required privileges inside a vulnerable virtual machine may be able to exploit the flaw and execute code on the host system.
That is the part administrators should care about.
Not another application crash.
Not another denial-of-service bug.
A possible path from the virtual machine to the machine running it.
Security researchers often describe this class of vulnerability as a VM escape.
The term sounds dramatic because it is.
Virtualization creates a security boundary between the guest and the host. Applications inside the VM are not supposed to be able to directly compromise the operating system underneath the hypervisor.
CVE-2026-59346 potentially changes that.
The vulnerable component is VMXNET3, VMware’s high-performance virtual network adapter used by guest operating systems.
A flaw in the communication path between the virtualized network device and the host-side virtualization process can therefore become a bridge across the isolation boundary.
And there is another problem.
Broadcom also addressed CVE-2026-59347, a stack-based buffer overflow vulnerability affecting the HGFS shared-folder functionality.
HGFS allows a virtual machine and its host to exchange files.
Convenient.
Also exactly the kind of feature that sits directly between two environments that are supposed to remain isolated.
A successful attack against the vulnerable component could allow code execution in the VMX process on the host.
Put the two vulnerabilities together and the security model starts looking considerably less comfortable.
One affects the virtual network adapter.
The other affects shared-folder functionality.
Both involve code operating across the guest-to-host boundary.
Broadcom has released security updates for affected VMware products and administrators should not treat this as an ordinary low-risk maintenance update.
There is currently no public indication that these vulnerabilities are being actively exploited in the wild.
That is the good news.
The bad news is that attackers do not need active exploitation to make a critical vulnerability worth patching.
Virtual machines frequently run software that administrators would never trust directly on the host.
Malware analysis environments.
Test servers.
Legacy operating systems.
Unknown software.
Customer workloads.
Development environments.
Sometimes intentionally malicious code.
That isolation is only useful if the boundary actually holds.
A VM escape vulnerability changes the threat model immediately.
An attacker who compromises a guest operating system normally remains trapped inside that guest.
With a successful host escape, the attacker may gain access to the underlying system and potentially reach other virtual machines running on the same hardware.
The impact therefore depends heavily on what the host is doing.
A developer laptop running one VM is one thing.
A workstation hosting multiple security labs is another.
A virtualization environment used to separate sensitive workloads is something else entirely.
The lesson is simple.
Virtualization is isolation. Not immunity.
Features that connect the guest and the host — network adapters, shared folders, clipboard integration and device passthrough — are useful.
They are also attack surface.
When a vulnerability appears inside those components, the attacker is no longer limited to attacking software inside the virtual machine.
They can start attacking the wall around it.
Administrators running VMware Workstation or Fusion should review Broadcom’s security advisory, identify affected installations and apply the appropriate updates as soon as possible.
If you use virtual machines to execute untrusted code, this one deserves priority.
The whole point of putting dangerous software inside a VM is to make sure it stays there.
Bugstoday’s take: A VM is supposed to be a cage. CVE-2026-59346 is a reminder that cages have locks, and locks have bugs. If attackers can turn a vulnerable virtual device into code execution on the host, the guest is no longer the end of the compromise. It is just the first room.
Today’s Bugs. Tomorrow’s Breaches.
Technical Sources
- Broadcom VMware Security Advisory
- CVE-2026-59346
- CVE-2026-59347
- VMware Workstation Security Updates
- VMware Fusion Security Updates
