Hypervisor escape in VMware ESX via VMXNET3; widely deployed virtualization, host compromise risk across enterprises.
CVE-2026-47876
VMware ESX VMXNET3 OOB write allows host code execution from a VM.
Is CVE-2026-47876 being exploited?
Not confirmed. CVE-2026-47876 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-47876?
CVE-2026-47876 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47876?
Not known from our data. No patch reference has been recorded for CVE-2026-47876, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-47876 affect?
CVE-2026-47876 affects VMware ESX/ESXi hosts with VMXNET3 adapter, Virtual machines using VMXNET3 network adapter. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47876?
Disable VMXNET3 on untrusted VMs, restrict VM admin access, isolate affected hosts, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local admin on a VM with VMXNET3 can execute code on the ESX host, leading to full host compromise and cross-VM impact.
Immediate action required
- affected9.1.x.x
- affected9.0.x.x
- affected5.x
- affected>= 9.1.x.x and < ESXi-9.1.0.0200-25557999
- affected>= 9.0.x.x and < ESXi-9.0.2.0100-25595025
- affected>= 8.0 and < ESXi80U3k-25595708
- affected5.1.x
- affected5.0.x
- affected9.1.x.x
- affected9.0.x.x
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.