VMware Workstation and Fusion contain an integer-overflow vulnerability. A malicious actor with...
Summary
Vulnerability reported (CVE-2026-59346). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 26H1u1 or later.
Original description
The description as published by the source.
VMware Workstation and Fusion contain an integer-overflow vulnerability. A malicious actor with local administrative privileges on a virtual machine with VMXNET3 virtual network adapter may exploit this issue to execute code on the host.
Affected versions:
- VMware Workstation: 25H2, 26H1 (fixed in 26H1u1)
- VMware Fusion: 25H2, 26H1 (fixed in 26H1u1)
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59346 has been found.
Successful exploitation can lead to full system takeover. CVSS score: 9.3/10.
What to do: upgrade the affected software to 26H1u1 or later.
If unsure, ask your IT team or search "CVE-2026-59346" on the vendor's site.
CVE-2026-59346 — CWE-190 / CVSS v3 9.3
Attack vector: local / unauthenticated / no user interaction
Patched: 26H1u1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-190) has been reported.
Check the vendor advisory for the affected versions.
Severity: Critical (CVSS 9.3/10). Successful exploitation can lead to full system takeover.
Update to 26H1u1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Apply patch patch
Upgrade to 26H1u1ステージング環境で 26H1u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web security@vmware.com
- web github.com