CVE-2025-62215: Microsoft Windows Race Condition Vulnerability
Microsoft · Windows · NVD published 2025-11-12 · posted 2025-11-12 · last modified 2026-06-17
What it is
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.
| Weakness | CWE-362CWE-415 |
|---|---|
| CVSS vector | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (source: [email protected]) |
| CISA due date | 2025-12-03 (for US federal agencies under BOD; a good deadline for everyone) |
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2025-11-12 (earliest date across the sources below).
Exploited in the wild
- CISA KEV: listed since 2025-11-12. Source
Public exploit code
Exploit-DB
- EDB-52494: Windows Kernel - Elevation of Privilege (2026-04-06)
GitHub proof-of-concept repositories
7 public repositories from 7 accounts, first seen 2025-11-18. Most starred: abrewer251/CVE-2025-62215_Windows_Kernel_PE (21 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: CISA KEV · Exploit-DB (OffSec) · nomi-sec/PoC-in-GitHub.
No ATT&CK techniques could be mapped or inferred for this CVE yet.
How to fix it
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)
Fixed versions
- microsoft windows 10 1809: upgrade to 10.0.17763.8027 or later
- microsoft windows 10 21h2: upgrade to 10.0.19044.6575 or later
- microsoft windows 10 22h2: upgrade to 10.0.19045.6575 or later
- microsoft windows 11 23h2: upgrade to 10.0.22631.6199 or later
- microsoft windows 11 24h2: upgrade to 10.0.26100.7092 or later
- microsoft windows 11 25h2: upgrade to 10.0.26200.7092 or later
- microsoft windows server 2019: upgrade to 10.0.17763.8027 or later
- microsoft windows server 2022: upgrade to 10.0.20348.4346 or later
- microsoft windows server 2022 23h2: upgrade to 10.0.25398.1965 or later
- microsoft windows server 2025: upgrade to 10.0.26100.7092 or later
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2025-62215 (CISA KEV notes)
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-62215 (Vendor Advisory)
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.