Skip to content
Fencer Vulns
medium 4.1

CVE-2022-24466 json

Windows Hyper-V Security Feature Bypass Vulnerability

published 2022-05-10 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-29347

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

Summary

Windows Hyper-V Security Feature Bypass Vulnerability

Patch / fix

  • Microsoft Windows 10 Version 1809 10.0.17763.2928
  • Microsoft Windows Server 2019 10.0.17763.2928
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.2928
  • Microsoft Windows 10 Version 1909 10.0.18363.2274
  • Microsoft Windows 10 Version 21H1 10.0.19043.1706
  • Microsoft Windows Server 2022 10.0.20348.707
  • Microsoft Windows Server version 20H2 10.0.19042.1706
  • Microsoft Windows 11 version 21H2 10.0.22000.675
  • Microsoft Windows 10 Version 21H2 10.0.19044.1706
  • Microsoft Windows 10 Version 1607 10.0.14393.5125
  • Microsoft Windows Server 2016 10.0.14393.5125
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.5125

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 4.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N/E:U/RL:O/RC:C
CNA 3.1 4.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
NVD 3.1 4.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
NVD 2.0 2.3 AV:A/AC:M/Au:S/C:N/I:P/A:N

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 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.