Skip to content
Fencer Vulns
high 7.9

CVE-2022-21995 json

Windows Hyper-V Remote Code Execution Vulnerability

published 2022-02-09 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-27149

cvss
7.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

Windows Hyper-V Remote Code Execution Vulnerability

Patch / fix

  • Microsoft Windows 10 Version 1809 10.0.17763.2565
  • Microsoft Windows Server 2019 10.0.17763.2565
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.2565
  • Microsoft Windows 10 Version 1909 10.0.18363.2094
  • Microsoft Windows 10 Version 21H1 10.0.19043.1526
  • Microsoft Windows Server 2022 10.0.20348.524
  • Microsoft Windows Server version 20H2 10.0.19042.1526
  • Microsoft Windows 11 version 21H2 10.0.22000.493
  • Microsoft Windows 10 Version 21H2 10.0.19044.1526
  • Microsoft Windows 10 Version 1507 10.0.10240.19204
  • Microsoft Windows 10 Version 1607 10.0.14393.4946
  • Microsoft Windows Server 2016 10.0.14393.4946
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.4946

Exploit prediction

0.97% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.9 CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 7.9 CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD 2.0 6.8 AV:A/AC:H/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Windows 10 Version 1809
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows 10 Version 1909
  • Microsoft Windows 10 Version 21H1
  • Microsoft Windows Server 2022
  • Microsoft Windows Server version 20H2
  • Microsoft Windows 11 version 21H2
  • Microsoft Windows 10 Version 21H2
  • Microsoft Windows 10 Version 1507
  • Microsoft Windows 10 Version 1607
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 (Server Core installation)

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.