What’s Vulnerable › Vulnerabilities
CVE-2019-0722: Windows Hyper-V Remote Code Execution Vulnerability
- Severity: critical (CVSS 9.0 v2.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 4.7% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2019-06-12 · updated 2026-06-17
- Weakness: CWE-20
Description
A remote code execution vulnerability exists when Windows Hyper-V on a host server fails to properly validate input from an authenticated user on a guest operating system. To exploit the vulnerability, an attacker could run a specially crafted application on a guest operating system that could cause the Hyper-V host operating system to execute arbitrary code. An attacker who successfully exploited the vulnerability could execute arbitrary code on the host operating system. The security update addresses the vulnerability by correcting how Hyper-V validates guest operating system user input.
Affected products
- Microsoft Windows 10 Version 1607: 1607, 1703, 1709, 1803, 1809, 1903
- Microsoft Windows 7: all versions
- Microsoft Windows 8.1: all versions
- Microsoft Windows RT 8.1: all versions
- Microsoft Windows Server 2008: r2-sp1
- Microsoft Windows Server 2012: r2
- Microsoft Windows Server 2016: 1803, 1903
- Microsoft Windows Server 2019: all versions
- Microsoft Windows 10 Version 1507: from 10.0.10240.0 before publication — fixed in publication
- Microsoft Windows 10 1607: from 10.0.14393.0 before publication — fixed in publication
- Microsoft Corporation Windows 10 1703: from 10.0.0 before publication — fixed in publication
- Microsoft Windows 10 1709: from 10.0.0 before publication — fixed in publication
- Microsoft Windows 10 1803: from 10.0.0 before publication — fixed in publication
- Microsoft Windows 10: from 10.0.17763.0 before publication — fixed in publication
- Microsoft Windows 10 Version 1903 for ARM64-based Systems: from 10.0.0 before publication — fixed in publication
- Microsoft Windows 10 Version 1903 for x64-based Systems: from 10.0.0 before publication — fixed in publication
- Microsoft Windows 7 Service Pack 1: from 6.1.0 before publication — fixed in publication
- Microsoft Windows 8.1: from 6.3.0 before publication — fixed in publication
- Microsoft Windows Server 2008 R2 Service Pack 1: from 6.1.7601.0 before publication — fixed in publication
- Microsoft Windows Server 2008 R2 Systems Service Pack 1: from 6.1.0 before publication — fixed in publication
- Microsoft Windows Server 2008 Service Pack 2: from 6.0.0 before publication — fixed in publication
- Microsoft Windows Server 2012: from 6.2.9200.0 before publication — fixed in publication
- Microsoft Windows Server 2012 R2: from 6.3.9600.0 before publication — fixed in publication
- Microsoft Windows Server 2016: from 10.0.14393.0 before publication — fixed in publication
- Microsoft Windows Server 2019: from 10.0.17763.0 before publication — fixed in publication
- Microsoft Windows Server, version 1803 (Server Core Installation): from 10.0.0 before publication — fixed in publication
- Microsoft Windows Server, version 1903 (Server Core installation): from 10.0.0 before publication — fixed in publication
How to fix
Upgrade to a fixed version: Microsoft Windows 10 Version 1507 publication; Microsoft Windows 10 1607 publication; Microsoft Corporation Windows 10 1703 publication; Microsoft Windows 10 1709 publication; Microsoft Windows 10 1803 publication; Microsoft Windows 10 publication; Microsoft Windows 10 Version 1903 for ARM64-based Systems publication; Microsoft Windows 10 Version 1903 for x64-based Systems publication; Microsoft Windows 7 Service Pack 1 publication; Microsoft Windows 8.1 publication; Microsoft Windows Server 2008 R2 Service Pack 1 publication; Microsoft Windows Server 2008 R2 Systems Service Pack 1 publication. Check the vendor advisory for mitigations.
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-0722
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0722
Get alerted when CVE-2019-0722 or the next vulnerability affects your stack