CVE-2023-36427Public exploit

Memory protection bypass via unintercepted HFI MSR writes

Published Nov 14, 2023 · Updated Oct 8, 2025

Hyper-V in affected Microsoft Windows builds allows local users to bypass protected physical-memory restrictions through HFI controls. Hyper-V does not intercept root-partition writes to the HFI pointer and configuration MSRs, so the processor writes HFI data to a chosen physical page without enforcing EPT permissions. Exploitation requires HFI-capable 12th-generation or newer Intel hardware, arbitrary kernel-memory and MSR writes, and a shutdown or hibernation transition; successful use corrupts protected memory and can crash the system.

CVSS severity7.0
High
EPSS probability1.49%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hyper-V in affected Microsoft Windows builds allows local users to bypass protected physical-memory restrictions through HFI controls. Hyper-V does not intercept root-partition writes to the HFI pointer and configuration MSRs, so the processor writes HFI data to a chosen physical page without enforcing EPT permissions. Exploitation requires HFI-capable 12th-generation or newer Intel hardware, arbitrary kernel-memory and MSR writes, and a shutdown or hibernation transition; successful use corrupts protected memory and can crash the system.

The record

CVE
CVE-2023-36427
Published
Nov 14, 2023
Updated
Oct 8, 2025
Vendor
Microsoft
Product
Windows Server 2019
Classifications
T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 14, 2023CVE publishedPublication date reported by the CVE source.
  2. Oct 8, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.17763.0 <10.0.17763.5122

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.5122
Microsoft · Windows 11 version 21H2version=10.0.0 <10.0.22000.2600
Microsoft · Windows 10 Version 21H2version=10.0.19043.0 <10.0.19043.3693
Microsoft · Windows Server 2022, 23H2 Edition (Server Core installation)version=10.0.25398.0 <10.0.25398.531
Microsoft · Windows 10 Version 22H2version=10.0.19045.0 <10.0.19045.3693
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.5122
Microsoft · Windows 11 Version 23H2version=10.0.22631.0 <10.0.22631.2715
Microsoft · Windows 11, version 22H2version=10.0.22621.0 <10.0.22621.2715
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.2113
Microsoft · Windows 10 Version 1809version=10.0.17763.0 <10.0.17763.5122

Published CVSS scores

7.0Microsoft CorporationCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
7.0NIST NVDCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1068Exploitation for Privilege Escalation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo