Broadcom has shipped security updates for VMware Workstation and Fusion addressing two vulnerabilities, the most severe of which — CVE-2026-59346 (CVSS 9.3) — is an integer-overflow flaw that allows a local attacker with elevated privileges inside a guest virtual machine to execute arbitrary code on the host operating system under certain conditions.
Let me be blunt about why this matters to your security posture, even if you think of Workstation and Fusion as "desktop" products. In every enterprise I assess, these hypervisors are installed on developer laptops, security research boxes, malware analysis sandboxes, build agents, and jump hosts. They routinely run untrusted code — detonated malware samples, third-party vendor appliances, CTF ranges, and customer-provided images. A guest-to-host escape in this class of software collapses the one boundary those use cases depend on. An attacker who achieves code execution on the host inherits whatever that host can reach: domain credentials in memory, source code, signing keys, and lateral movement paths into production.
A second, lower-severity vulnerability was patched in the same advisory. Even without full details on the companion bug, the remediation path is identical: patch both products immediately.
Technical Analysis
Affected Products
- VMware Workstation Pro (Windows and Linux hosts)
- VMware Fusion Pro (macOS hosts)
Both products share significant hypervisor codebase (the vmware-vmx process / virtual machine monitor), which is why a single flaw frequently lands in both advisories simultaneously. Organizations running any unpatched build prior to the current release should assume exposure.
The Vulnerability: CVE-2026-59346
- Class: Integer overflow (CWE-190), leading to memory corruption
- CVSS v3.x Score: 9.3 (Critical)
- Attack vector: Local — from within a guest VM
- Privilege requirement: Elevated privileges inside the guest (administrator/root in the VM)
- Impact: Arbitrary code execution on the host OS
Integer overflows in hypervisor code are a classic VM escape primitive. The typical exploitation pattern works like this: the guest OS communicates with the hypervisor through virtualized device interfaces (paravirtualized devices, shared folders, drag-and-drop/copy-paste services, graphics/virtual GPU components, backdoor RPC channels). A size or length field supplied by the guest is used in an arithmetic operation — an allocation size calculation, an index computation, or a bounds check — without adequate validation. When the arithmetic wraps, the hypervisor allocates or validates against a small value but subsequently writes or copies using a much larger one, producing a heap or stack corruption in the context of the vmware-vmx process on the host. Because vmware-vmx runs with the privileges of the host user who launched the VM (frequently a developer or admin with broad local and domain access), attacker-controlled code execution in that process is a full host compromise in practical terms.
The privilege requirement — admin inside the guest — should not lull you into complacency. Consider the scenarios where the guest is supposed to be hostile: malware analysis VMs, detonation environments, red team tooling VMs, and third-party software evaluation. In all of these, "the attacker has root inside the guest" is the baseline assumption, not a mitigating factor.
Exploitation Status
At time of publication, Broadcom's advisory does not indicate confirmed in-the-wild exploitation, and there is no public proof-of-concept code. However, the history of this product class is instructive: VMware escape vulnerabilities are consistently targeted by sophisticated actors and by exploit developers for the Pwn2Own circuit, and the gap between disclosure and weaponization for virtualization escapes has historically been measured in weeks. Treat this as pre-weaponization critical exposure. If CVE-2026-59346 appears in the CISA Known Exploited Vulnerabilities catalog, your remediation clock shrinks dramatically — monitor the KEV feed.
Detection & Response
Post-exploitation detection of a VM escape centers on one high-fidelity behavioral signal: the hypervisor worker process (vmware-vmx.exe) doing things a hypervisor should never do. A healthy vmware-vmx.exe manages virtual hardware, talks to virtual devices, and performs heavy memory and I/O operations. It does not spawn shells, script interpreters, downloaders, or reconnaissance tooling. Any child process of vmware-vmx.exe is a strong VM escape indicator. The same logic applies to child processes of the VMware host services (vmware-authd.exe, vmware-hostd.exe).
Sigma Rules
---
title: VMware vmware-vmx Spawning Shell or Script Interpreter - Possible VM Escape
description: Detects vmware-vmx.exe spawning command shells, script interpreters, or LOLBins. The virtual machine monitor process should never spawn interactive tooling; this is a high-fidelity indicator of guest-to-host escape (e.g., CVE-2026-59346 exploitation) achieving code execution on the host.
references:
- https://thehackernews.com/2026/09/critical-vmware-workstation-and-fusion.html
- https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/09/10
status: experimental
id: 4f7c2a91-3b8d-4e56-a921-7d5e0c6b1f34
tags:
- attack.execution
- attack.t1059
- attack.privilege_escalation
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\vmware-vmx.exe'
- '\vmware-authd.exe'
- '\vmware-hostd.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
- '\certutil.exe'
- '\bitsadmin.exe'
- '\wmic.exe'
- '\curl.exe'
condition: selection_parent and selection_child
falsepositives:
- Extremely rare. Legitimate VMware tools operations execute inside the guest, not as children of the host vmx process.
level: critical
---
title: VMware vmware-vmx Writing Executable Content to Host File System
description: Detects the vmware-vmx.exe process dropping executable or script files to user-writable host locations (Temp, AppData, ProgramData, Public). Post-escape payload staging frequently originates from the compromised vmx process context.
references:
- https://thehackernews.com/2026/09/critical-vmware-workstation-and-fusion.html
- https://attack.mitre.org/techniques/T1105/
author: Security Arsenal
date: 2026/09/10
status: experimental
id: 8a1e5d37-9c42-4f7b-b3e6-2c9a4d8e5f61
tags:
- attack.execution
- attack.t1105
logsource:
category: file_event
product: windows
detection:
selection_image:
Image|endswith: '\vmware-vmx.exe'
selection_path:
TargetFilename|contains:
- '\AppData\'
- '\Temp\'
- '\ProgramData\'
- '\Users\Public\'
selection_ext:
TargetFilename|endswith:
- '.exe'
- '.dll'
- '.ps1'
- '.bat'
- '.cmd'
- '.vbs'
- '.js'
condition: selection_image and selection_path and selection_ext
falsepositives:
- VMware logging writes text logs to user directories; the extension filter excludes these.
- Rare VMware tooling self-update components writing DLLs — validate against known VMware signed paths.
level: high
---
title: VMware Workstation or Fusion Hypervisor Process Crash Artifacts
description: Detects Windows Error Reporting artifacts and crash dumps for vmware-vmx.exe. Repeated or clustered vmx crashes may indicate exploitation attempts against memory-corruption flaws such as CVE-2026-59346 integer overflow, including failed exploit attempts.
references:
- https://thehackernews.com/2026/09/critical-vmware-workstation-and-fusion.html
author: Security Arsenal
date: 2026/09/10
status: experimental
id: 2b6d9f14-7e38-4a1c-95d2-6f3b8a0c4e27
tags:
- attack.exploitation
- attack.t1068
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\WerFault.exe'
- '\wermgr.exe'
CommandLine|contains:
- 'vmware-vmx'
condition: selection
falsepositives:
- Legitimate vmx instability from driver conflicts or resource exhaustion. Investigate clustered occurrences on the same host.
level: medium
KQL — Microsoft Sentinel / Defender
This query hunts for the core escape indicator — the hypervisor process spawning interactive or scripting children — and enriches with initiating account context for triage:
// Hunt: VM escape indicator — VMware hypervisor processes spawning unexpected children (CVE-2026-59346 post-exploitation)
let VMwareHostProcs = dynamic(["vmware-vmx.exe", "vmware-authd.exe", "vmware-hostd.exe", "vmware-vmx-debug.exe"]);
let SuspiciousChildren = dynamic(["cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe", "certutil.exe", "bitsadmin.exe", "wmic.exe", "curl.exe", "net.exe", "whoami.exe", "ipconfig.exe"]);
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where InitiatingProcessFileName in~ (VMwareHostProcs)
| where FileName in~ (SuspiciousChildren)
| project TimeGenerated, DeviceName, AccountName = InitiatingProcessAccountName,
HypervisorProcess = InitiatingProcessFileName, InitiatingProcessCommandLine,
SpawnedProcess = FileName, ProcessCommandLine, SHA256, FolderPath
| sort by TimeGenerated desc
// Correlate with vmx crash events (possible failed exploit attempts)
;
DeviceProcessEvents
| where TimeGenerated > ago(14d)
| where FileName in~ ("WerFault.exe", "wermgr.exe")
| where ProcessCommandLine has "vmware-vmx"
| project TimeGenerated, DeviceName, FileName, ProcessCommandLine, InitiatingProcessAccountName
For environments forwarding Linux host syslog to Sentinel (Workstation on Linux), hunt for shells or downloaders parented by the vmx process:
// Linux hosts: vmware-vmx spawning shells/downloaders — ingested via Syslog/CEF
Syslog
| where TimeGenerated > ago(14d)
| where ProcessName =~ "vmware-vmx"
| where SyslogMessage has_any ("/bin/sh", "/bin/bash", "curl ", "wget ", "nc ", "python", "perl")
| project TimeGenerated, Computer, ProcessName, SyslogMessage
| sort by TimeGenerated desc
Velociraptor VQL
Deploy this hunt across Windows endpoints running Workstation to enumerate vmx processes with anomalous child processes or unsigned injected modules:
-- Hunt for VMware vmware-vmx processes with suspicious child processes
-- Indicator of guest-to-host escape exploitation (CVE-2026-59346 post-exploitation)
SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Ppid IN (
SELECT Pid FROM pslist()
WHERE Name =~ 'vmware-vmx|vmware-authd|vmware-hostd'
)
AND Name =~ 'cmd|powershell|pwsh|wscript|cscript|mshta|rundll32|regsvr32|certutil|bitsadmin|wmic|curl'
-- Inventory installed VMware Workstation versions for patch-gap assessment
SELECT Name, Version, InstallLocation, Publisher
FROM artifact.Windows.Registry.Installation()
WHERE Name =~ 'VMware Workstation'
Remediation Script
Use this PowerShell script to inventory VMware Workstation installations, verify the installed build, and confirm the hypervisor processes in memory match the patched binaries. Run elevated on endpoints; deploy via your RMM or Intune for fleet-wide coverage.
# CVE-2026-59346 - VMware Workstation inventory and patch verification
# Run as Administrator. Deploy via RMM/Intune/SCCM for fleet coverage.
$results = @()
# 1. Locate installed VMware products via registry uninstall keys
$uninstallPaths = @(
'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*',
'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'
)
$vmware = Get-ItemProperty $uninstallPaths -ErrorAction SilentlyContinue |
Where-Object { $_.DisplayName -match 'VMware Workstation' }
foreach ($app in $vmware) {
$results += [PSCustomObject]@{
Product = $app.DisplayName
Version = $app.DisplayVersion
Publisher = $app.Publisher
InstallDate = $app.InstallDate
Host = $env:COMPUTERNAME
}
}
# 2. Check file version of the vmware-vmx.exe binary directly
$vmxPath = "$env:ProgramFiles(x86)\VMware\VMware Workstation\vmware-vmx.exe"
if (-not (Test-Path $vmxPath)) {
$vmxPath = "$env:ProgramFiles\VMware\VMware Workstation\x64\vmware-vmx.exe"
}
if (Test-Path $vmxPath) {
$fileVer = (Get-Item $vmxPath).VersionInfo
$results += [PSCustomObject]@{
Product = 'vmware-vmx.exe'
Version = $fileVer.ProductVersion
Publisher = $fileVer.CompanyName
InstallDate = (Get-Item $vmxPath).LastWriteTime.ToString('yyyyMMdd')
Host = $env:COMPUTERNAME
}
}
# 3. Flag running VMs (hypervisor processes) that predate patching — must be restarted to load patched code
$vmxProcs = Get-Process -Name 'vmware-vmx' -ErrorAction SilentlyContinue
foreach ($p in $vmxProcs) {
$results += [PSCustomObject]@{
Product = 'RUNNING VM PROCESS (restart required after patch)'
Version = $p.StartTime.ToString('yyyy-MM-dd HH:mm')
Publisher = $p.Path
InstallDate = ''
Host = $env:COMPUTERNAME
}
}
$results | Format-Table -AutoSize
$results | Export-Csv -Path "$env:TEMP\vmware_cve_2026_59346_audit.csv" -NoTypeInformation
Write-Output "Audit complete. Compare installed builds against the fixed versions in Broadcom advisory. Guests must be powered off and vmware-vmx restarted for the patched hypervisor to load."
On macOS (Fusion) and Linux (Workstation) hosts, this Bash snippet performs equivalent inventory:
# macOS Fusion: report installed version and check for running VM processes predating patch
defaults read /Applications/VMware\ Fusion.app/Contents/Info.plist CFBundleShortVersionString 2>/dev/null || echo "Fusion not installed at default path"
ps aux | grep -i 'vmware-vmx' | grep -v grep
# Linux Workstation: report installed version and running vmx processes
vmware --version 2>/dev/null || echo "vmware CLI not found"
rpm -qa 2>/dev/null | grep -i vmware || dpkg -l 2>/dev/null | grep -i vmware
ps aux | grep '[v]mware-vmx'
Remediation
- Patch immediately. Apply the current fixed release of VMware Workstation Pro and Fusion Pro per Broadcom's advisory. Download patched installers only from the official Broadcom support portal (support.broadcom.com) and the VMware security advisory page for this release. Verify digital signatures on installers before deployment.
- Restart matters. Patching the binaries on disk is not sufficient — running guest VMs continue executing under the old
vmware-vmxcode loaded in memory. Schedule a maintenance window to fully power off all running guests and restart the hypervisor processes (or reboot the host) after patching. This is the step that gets skipped in every rushed patch cycle. - Enforce the patch with your VMS. Feed CVE-2026-59346 into your vulnerability management platform as a Critical finding scoped to every endpoint with Workstation or Fusion installed — including developer laptops, which frequently fall outside standard server SLA windows. Do not let "endpoint" status exempt these hosts from a 9.3 SLA.
- Prioritize hostile-guest environments. Malware analysis workstations, detonation sandboxes, and security research VMs are the highest-risk population. Patch these first — the exploitation precondition (privileged code in the guest) is their normal operating state.
- Reduce attack surface until patched. Where immediate patching is blocked, disable non-essential guest integration features: shared folders (HGFS), drag-and-drop, copy/paste, and virtual printing. Isolate VM-running hosts from flat network access to production segments and restrict local admin/domain logon rights on those machines so a host compromise yields less.
- Never run Workstation/Fusion sessions under privileged host accounts. Launch VMs from a standard user context; avoid interactive logon to VM hosts with domain admin or enterprise admin credentials, which limits post-escape credential theft.
- Monitor CISA KEV. If CVE-2026-59346 enters the Known Exploited Vulnerabilities catalog, federal binding operational directive timelines and your own policy-driven emergency patch SLAs apply. Subscribe to the KEV feed and Broadcom security advisory mailing list.
Analyst Note
The SOC detection strategy here is deliberately narrow. You cannot signature an integer overflow in closed-source hypervisor code — but you can watch for what an escape produces: the vmx process acting like an attacker. A child shell under vmware-vmx.exe is as close to a zero-noise critical alert as you'll find on a Windows endpoint. Wire it into your EDR and SIEM today, before the PoC drops.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.