Windows Kernel Elevation of Privilege Vulnerability
Windows 11 24H2, 25H2 and 26H1 and Windows Server 2025 builds below the listed fixed versions are covered. No vendor severity is given; the CVSS score is 7.8.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 10.0.26100.9168, 10.0.26200.9168, 10.0.28000.2704, 10.0.26100.33296
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 2 proofs of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Untrusted pointer dereference in Windows Kernel allows an authorized attacker to elevate privileges locally.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Microsoft Windows 11 Version 24H2
From 10.0.26100.0 · fixed in 10.0.26100.9168
- Microsoft Windows 11 Version 25H2
From 10.0.26200.0 · fixed in 10.0.26200.9168
- Microsoft Windows 11 version 26H1
From 10.0.28000.0 · fixed in 10.0.28000.2704
- Microsoft Windows Server 2025
From 10.0.26100.0 · fixed in 10.0.26100.33296
- Microsoft Windows Server 2025 (Server Core installation)
From 10.0.26100.0 · fixed in 10.0.26100.33296
References 3
msrc.microsoft.com
GitHub · DavidCarliez/cve-2026-62737-lab
GitHub · loanvui/CVE-2026-62737
Questions about CVE-2026-62737
What does this mean?
The flaw gives an arbitrary kernel-mode call primitive that can crash the kernel, causing denial of service. The advisory says a lab-only chain built on it is not a standalone exploit.Source: github.com, github.com
Am I affected, and how do I check?
Affected builds are Windows 11 24H2 below 10.0.26100.9168, 25H2 below 10.0.26200.9168, 26H1 below 10.0.28000.2704, and Windows Server 2025 (including Server Core) below 10.0.26100.33296. Check your build number with the winver command. The vulnerable kernel path sits behind an internal feature flag that is disabled on stock 24H2 build 26100.5074 x64.Source: github.com, github.com
What should I do about it?
Install the update that brings your product to its fixed build: 10.0.26100.9168 for Windows 11 24H2, 10.0.26200.9168 for 25H2, 10.0.28000.2704 for 26H1, or 10.0.26100.33296 for Windows Server 2025.Source: github.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data