Skip to main content

VMware Workstation EUVDEUVD-2026-94169

| CVE-2026-59347 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-10-07 vmware GHSA-54rf-87fx-f97x
8.1
CVSS 3.1 · Vendor: vmware
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local admin in guest VM
  2. Delivery
    Craft malformed HGFS requests
  3. Exploit
    Trigger stack buffer overflow in VMX
  4. Execution
    Execute code as host VMX process
  5. Impact
    Escape guest and compromise host

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to already hold local administrative privileges inside a guest VM running on an affected build of VMware Workstation or Fusion (25H2 or 26H1), and requires the HGFS feature (Host-Guest File System, used for shared folders between host and guest) to be reachable from the guest. Limiting factors that reduce realistic risk: the attacker must first fully compromise a guest to admin level (local, pre-authenticated foothold required), the CVSS AC:H indicates exploitation of the stack overflow is non-trivial and must overcome host memory protections, and the issue is remediated by updating to Workstation/Fusion 26H1u1. This makes the flaw most relevant to untrusted-guest or multi-tenant deployments rather than to single-trusted-user desktops.

Impact

This is a VMware guest-to-host escape in the HGFS (Host-Guest File System / shared folders) component, which is a genuinely high-value class of flaw because it breaks the primary security boundary of virtualization. The vendor CVSS vector (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, base 8.1) reflects local attack vector, high exploitation complexity, a scope change from guest to host, and full confidentiality/integrity/availability impact on the host. Note an apparent conflict: the vector lists PR:N (no privileges) while the description explicitly requires 'local administrative privileges on a virtual machine' - this is VMware's standard scoring convention, where PR is measured against the vulnerable component's authority (the host VMX process), on which the attacker holds no privileges, even though they must already be admin inside the guest. In practical terms this is NOT a remote-unauthenticated issue: an attacker must already fully control a guest VM. No EPSS score, CISA KEV listing, or POC availability was provided in the input, so there is no signal of active or widespread exploitation; combined with AC:H (buffer-overflow exploitation defeating modern mitigations is non-trivial), this is best treated as a serious-but-not-emergency patch priority. The real risk concentrates in multi-tenant or untrusted-guest scenarios (malware analysis labs, shared desktop virtualization, CI runners) where an attacker plausibly holds guest admin; in single-user developer-desktop deployments the practical exposure is far lower.

Exploit ScenarioDerived

An attacker who has already obtained administrative access inside a guest virtual machine (e.g., via malware detonation in an analysis sandbox or a compromised VM) sends specially crafted HGFS requests to the host. These overflow a stack buffer in the VMX process, allowing the attacker to execute arbitrary code with the privileges of the host-side VMX process and escape the VM. No public exploit code was identified at time of analysis, and the high attack complexity (AC:H) means reliable exploitation requires defeating host-side memory protections.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

VMware Workstation and Fusion (25H2 and 26H1) carry a stack-based buffer overflow in the HGFS Host-Guest File System component used for shared folders, letting an attacker who already holds administrative privileges inside a guest VM execute code as the VMX process on the host and thereby break the guest-to-host isolation boundary. This is a VMware guest-to-host escape, a genuinely high-value class of flaw because it defeats the primary security boundary of virtualization, though the realities of exploitation are gated: the attacker needs a pre-existing local admin foothold in the guest, HGFS must be reachable, and the CVSS vector's AC:H signals that the overflow must be shaped to bypass host memory protections. Vendor-released patch is available in Workstation/Fusion 26H1u1; no CISA KEV listing and no public exploit code was identified at time of analysis, and no EPSS score was supplied in the source data, so the practical risk concentrates on multi-tenant, untrusted-guest, or shared-lab deployments rather than single-user desktops.

RemediationAI

The primary fix is to update VMware Workstation and VMware Fusion to 26H1u1, the vendor-released patch version that resolves CVE-2026-59347, applying the Broadcom/Security-Response-Center advisory at https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/security-advisories/0/38288 for the exact build mapping. Because the flaw is only reachable when HGFS is in use, a viable interim compensating control is to disable shared folders / HGFS for every guest on an affected build, which removes the attack surface entirely at the cost of losing host-guest file sharing and any workflows that depend on it; where shared folders are essential, restrict them to trusted, single-owner VMs, avoid running untrusted or tenant-controlled guest images on 25H2/26H1 hosts, and treat any guest in which an attacker has obtained administrative rights as a potential host-compromise vector. Note that this is a local, guest-initiated flaw, so host firewalls, network segmentation, and edge hardening provide no protection; the patch is the only complete mitigation, and hypervisors should be treated as high-value endpoints for update priority given the Scope:Changed impact.

Affected VersionsENISA

VMware Fusion 25H2 ≤26H1
VMware Workstation 25H2 ≤26H1

Affected Packages

euvd vmware_fusion no fix
euvd vmware_workstation no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a CWE-121 stack-based buffer overflow in HGFS, the Host-Guest File System that implements shared folders between a VMware guest and its host. HGFS requests are processed by host-side code associated with the virtual machine's VMX process, which is why a successful overflow yields code execution as VMX on the host rather than merely crashing the guest. The CVSS:3.1 vector AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H is notable for Scope:Changed, the formal expression of a boundary crossing: the vulnerable component sits in the guest-facing HGFS path, but the exploited component is host-side. AC:H reflects the memory-corruption work required to turn the overflow into reliable code execution against host protections, and PR:N describes privileges relative to the host-side component even though the vendor assessment requires the attacker to already hold administrative rights inside the guest, since HGFS access from a guest is typically mediated through that guest's own privileged interfaces. The two CPEs, cpe:2.3:a:vmware:vmware_workstation and cpe:2.3:a:vmware:vmware_fusion, confirm both desktop hypervisor product lines are in scope for the same underlying HGFS code path, and the single Broadcom advisory reference indicates this was disclosed and fixed as one coordinated VMware security advisory rather than separate per-product issues.

Know when Vmware Workstation gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vmware) PRIMARY 8.1 HIGH
AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

AV:L and AC:H for in-guest exploitation of a hard-to-trigger overflow; PR:N because the host VMX authority grants the attacker no privileges; S:C with C/I/A:H for full guest-to-host escape.

3.1 AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (vmware).

CVSS VectorVendor: vmware

Attack Vector
Local
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

VMware Workstation and Fusion contain a stack-based buffer-overflow vulnerability in HGFS. A malicious actor with local administrative privileges on a virtual machine may exploit this issue to execute code as the virtual machine's VMX process running on the host.

Affected versions:

  • VMware Workstation: 25H2, 26H1 (fixed in 26H1u1)
  • VMware Fusion: 25H2, 26H1 (fixed in 26H1u1)

Executive ViewAI

Why It Matters

A high-severity flaw in VMware Workstation and Fusion (25H2 and 26H1) allows code running inside a guest virtual machine to break out onto the host, undermining the virtualization boundary that our endpoint, engineering, and lab environments rely on to keep untrusted workloads contained. The practical exposure is concentrated in teams that run multi-tenant, third-party, or untrusted guest images - for example developer sandboxes, malware analysis labs, and testing environments - where an attacker already holding administrative rights inside a guest could reach host-level execution. Leadership should care because the guest-to-host isolation boundary is the primary control protecting shared physical hardware and the corporate data and credentials resident on it; a successful escape effectively converts a contained virtual workload into a host compromise. Vendor remediation is available, so the risk is manageable through prompt upgrade rather than architectural change.

Business Impact: High
Compensating Controls

Apply vendor patch (Workstation/Fusion 26H1u1). Where immediate upgrade is not feasible, disable shared folders/HGFS, restrict local administrative privileges inside guests, and avoid running untrusted or third-party guest images on unpatched hosts.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
High
widely deployed desktop/developer hypervisors, large but non-server install base
Social Media
8
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy