CVE-2025-62215 Microsoft Windows Race Condition Vulnerability
Microsoft Windows Kernel contains a race condition vulnerability that allows a local attacker with low-level privileges to escalate privileges. Successful exploitation of this vulnerability could enable the attacker to gain SYSTEM-level access.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 12 Nov 2025.
- Rated High severity (CVSS 7.0, scored by Vendor).
- It has been in the catalogue for 359 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.
Affected Versions
| Product | Versions |
|---|---|
| Microsoft Windows 10 Version 1809 | 10.0.17763.0 to before 10.0.17763.8027 |
| Microsoft Windows 10 Version 21H2 | 10.0.19044.0 to before 10.0.19044.6575 |
| Microsoft Windows 10 Version 22H2 | 10.0.19045.0 to before 10.0.19045.6575 |
| Microsoft Windows 11 version 22H3 | 10.0.22631.0 to before 10.0.22631.6199 |
| Microsoft Windows 11 Version 23H2 | 10.0.22631.0 to before 10.0.22631.6199 |
| Microsoft Windows 11 Version 24H2 | 10.0.26100.0 to before 10.0.26100.7171 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-62215 and every other exploited flaw on the list.