Skip to content
Fencer Intel
high 8.4

CVE-2026-45641 json

Windows Hyper-V Remote Code Execution Vulnerability

published 5mo ago modified last mo. also EUVD-2026-35687

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

Summary

Access of resource using incompatible type ('type confusion') in Windows Hyper-V allows an unauthorized attacker to execute code locally.

Patch / fix

  • Microsoft Windows 10 Version 21H2 10.0.19044.7417
  • Microsoft Windows 10 Version 22H2 10.0.19045.7417
  • Microsoft Windows 11 Version 23H2 10.0.22631.7219
  • Microsoft Windows 11 Version 24H2 10.0.26100.8655
  • Microsoft Windows 11 Version 25H2 10.0.26200.8655
  • Microsoft Windows 11 version 26H1 10.0.28000.2269
  • Microsoft Windows Server 2022 10.0.20348.5256
  • Microsoft Windows Server 2025 10.0.26100.32995
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.32995

Is CVE-2026-45641 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
4mo ago

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Windows 10 Version 21H2
  • Microsoft Windows 10 Version 22H2
  • Microsoft Windows 11 Version 23H2
  • Microsoft Windows 11 Version 24H2
  • Microsoft Windows 11 Version 25H2
  • Microsoft Windows 11 version 26H1
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type
  • CWE-125 Out-of-bounds Read

References

Sources

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