VMware and water systems exposed

A desktop virtualization boundary is back in focus

Broadcom’s September 3 advisory for VMware Workstation and VMware Fusion is not just another routine patch notice. It targets a core assumption behind desktop virtualization: that a guest machine can be used for risky work without immediately endangering the host. Broadcom says VMware Workstation and Fusion contain an integer-overflow vulnerability in VMXNET3, tracked as CVE-2026-59346, that can let a malicious actor with local administrative privileges on a virtual machine execute code on the host when the VM uses the VMXNET3 virtual network adapter [1].

A second vulnerability, CVE-2026-59347, is a stack-based buffer overflow in HGFS, VMware’s host-guest file-sharing component, and Broadcom says it can let an actor with local administrative privileges in a virtual machine execute code as the VMX process running on the host [1]. Broadcom rates the overall advisory critical, lists a CVSS range of 8.1 to 9.3, and names VMware Workstation and VMware Fusion as the impacted products [1].

The immediate fix is version 26H1u1 for both VMware Workstation and VMware Fusion, covering the affected 25H2 and 26H1 lines [1]. NHS England Digital separately alerted organizations that the flaws could lead to arbitrary code execution on a host system from an affected virtual machine and encouraged affected users to apply the relevant update as soon as possible [3].

What makes CVE-2026-59346 especially serious

CVE-2026-59346 is the headline risk because it crosses the guest-host boundary. Broadcom’s wording is precise: the attacker needs local administrative privileges inside a VM and the VM must use the VMXNET3 virtual network adapter, but the outcome is host code execution [1]. That matters because many Workstation and Fusion deployments are used exactly where users handle sensitive material: development laptops, malware-analysis sandboxes, security labs, support workstations and engineering machines.

In practice, administrative access inside a virtual machine is not an exotic condition. Developers often run test VMs with broad local privileges. Researchers may intentionally detonate suspicious files in isolated guests. IT teams may run legacy software, VPN clients or customer support images inside VMs to separate them from the main workstation. The risk is that an initial guest compromise, once paired with the vulnerability conditions, can become a host compromise.

SecurityWeek reported on September 4 that both vulnerabilities affect VMware Workstation and Fusion 25H2 and 26H1 and are resolved in 26H1u1 [2]. It also reported that Broadcom did not mention in-the-wild exploitation and said the issues were privately reported [2]. Tenable’s plugin page for VMware Workstation 25H2 and 26H1.x before 26H1u1 likewise states that no known exploits are available, while still classifying the plugin as critical and advising users to update [5].

Why “local admin in the VM” should not reduce urgency

Some organizations may be tempted to downgrade the risk because exploitation requires administrative privileges in the guest. That would be a mistake. A VM is often treated as a controlled blast chamber precisely because compromise of the guest is expected or at least tolerated. Malware analysis, exploit testing, package evaluation, browser testing and customer-environment reproduction all create situations in which the guest is intentionally exposed to untrusted code.

The correct reading is therefore not “the attacker already needs to be admin.” It is “if the guest falls, the host boundary may fail.” That is a different risk model. A compromised host can expose SSH keys, browser sessions, corporate identity tokens, source code, password vault integrations, endpoint management agents, cloud credentials and files mounted from shared folders. It can also undermine other VMs on the same workstation or give an attacker a more trusted foothold on the corporate network.

CVE-2026-59347 reinforces that point because HGFS is tied to one of the most convenient but security-sensitive features in desktop virtualization: file movement between guest and host. Broadcom says the HGFS stack buffer-overflow issue can allow code execution as the virtual machine’s VMX process on the host [1]. Even when the host operating system remains protected by its own controls, code running in a virtualization process is a serious escalation point.

No workaround means patching is the control

Broadcom lists no workarounds for either CVE-2026-59346 or CVE-2026-59347 [1]. That shifts the operational answer from mitigation-by-configuration to inventory and patch execution. Security teams should identify every instance of VMware Workstation and Fusion, including installations on developer machines, lab systems, contractor laptops, jump boxes and unmanaged endpoints.

The affected products and versions are narrow enough to make the first pass practical: Workstation 25H2 and 26H1, and Fusion 25H2 and 26H1, should be checked and moved to 26H1u1 [1]. CERT-FR’s September 4 notice also lists Fusion versions earlier than 26H1u1 and Workstation versions earlier than 26H1u1 as affected and directs users to the vendor bulletin for patches [4].

For larger organizations, the hard part may be discovering the software rather than installing the update. Workstation and Fusion often live outside server patching dashboards. They may be on privileged users’ laptops, in training labs or on machines controlled by small engineering teams. Endpoint management, EDR software inventory, vulnerability scanners and software asset tools should all be queried because relying on procurement records alone will miss free, old or manually installed copies.

The broader lesson: virtualization is a boundary, not a guarantee

This advisory is a reminder that virtualization remains software. It can be hardened, monitored and isolated, but it cannot be treated as an unbreakable wall. The boundary between guest and host is only as strong as the hypervisor code, virtual devices, sharing services and management features that implement it.

The VMware case is particularly instructive because both vulnerabilities touch common convenience layers: VMXNET3 networking and HGFS file sharing [1]. Those components exist to make VMs usable and fast, but they also expand the attack surface. Organizations that use VMs for risky activity should reassess defaults: disable unneeded virtual devices, limit shared folders, avoid unnecessary clipboard and drag-and-drop sharing, segment lab hosts, and keep host credentials out of guest workflows wherever possible.

Monitoring also matters. A patched host is the priority, but defenders should still review suspicious behavior around VMware processes, unexpected child processes spawned from virtualization components, unusual writes to shared folders, unexpected network activity from lab hosts and privilege changes inside guests used for analysis or testing. The absence of known exploitation as of the latest public reports is reassuring, but not a reason to delay [2][5].

What to do now

The practical response is straightforward. First, inventory VMware Workstation and Fusion installations. Second, verify whether they are on 25H2 or 26H1. Third, update to 26H1u1. Fourth, confirm the update with endpoint inventory or a vulnerability scan rather than accepting user self-reporting.

Fifth, review how VMs are used. If a workstation handles production credentials, source code or customer data, do not let high-risk guest activity share the same trust zone without compensating controls. Sixth, treat guest administrative access as meaningful attacker progress, not as a harmless sandbox condition. Finally, document the exception cases: legacy VMs, offline labs and systems that cannot be patched immediately should be isolated until they can be updated.

Broadcom’s advisory is focused, but the lesson is broad. A desktop hypervisor can reduce risk, yet it also concentrates risk when users trust it too much. The safest assumption after this disclosure is simple: patch the host, reduce the guest-host bridges, and monitor the workstation as though a VM escape is a realistic endpoint compromise path.

Sources from the last 72 hours

1. [1]VMware Workstation and Fusion Updates Patch Critical VulnerabilitySep 4, 2026, 11:42 AM UTC
2. [2]Broadcom Releases Security Advisory for Critical Vulnerabilities in VMware Workstation and VMware FusionSep 3, 2026, 1:57 PM UTC
3. [3]Multiples vulnérabilités dans les produits VMwareSep 4, 2026, 12:00 AM UTC

AI-generated article based on recent web research, then preserved as a dated editorial snapshot.