CVE-2025-62215: Microsoft Windows Race Condition
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-11-12.
- CVSS v3.1 (CVE record)
- 7.0
- high
- EPSS (exploit probability, 30 days)
- 4.5%
- higher than 91.6% of all CVEs
- Added to CISA KEV
- 2025-11-12
- US federal due date 2025-12-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-62215 explained
CVE-2025-62215 is a race condition in the Windows Kernel that lets an authorized local attacker elevate privileges. It affects multiple Windows 10, Windows 11 and Windows Server releases. CISA lists it as known exploited, so attackers are using it in real attacks, which makes prompt patching important.
Impact
An attacker who already has low-privileged local access can exploit improper synchronization in the Windows Kernel to gain higher privileges. No user interaction is needed, but attack complexity is high. A successful attack can fully compromise confidentiality, integrity and availability. CISA rates the technical impact as total and the vulnerability as not automatable, so each attack needs manual effort. CISA confirms active exploitation; ransomware use is unknown.
Who is affected
The CVE record lists Windows 10 Version 1809 and Windows Server 2019, including Server Core (fixed in 10.0.17763.8027); Windows 10 21H2 (10.0.19044.6575) and 22H2 (10.0.19045.6575); Windows 11 22H3 and 23H2 (10.0.22631.6199); Windows 11 24H2 and Windows Server 2025 (10.0.26100.7171); Windows 11 25H2 (10.0.26200.7171); Windows Server 2022 (10.0.20348.4405); and Windows Server 2022, 23H2 Edition Server Core (10.0.25398.1965). Builds below these are affected.
Written with AI from the data on this page and checked against it automatically.
Official description
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.
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.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 180932-bit, x64AffectedFixed in
- < 10.0.17763.8027
- 10.0.17763.8027
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.6575
- 10.0.19044.6575
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.6575
- 10.0.19045.6575
- Microsoft Windows 11 version 22H3ARM64AffectedFixed in
- < 10.0.22631.6199
- 10.0.22631.6199
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.6199
- 10.0.22631.6199
- Microsoft Windows 11 Version 24H2ARM64, x64AffectedFixed in
- < 10.0.26100.7171
- 10.0.26100.7171
- Microsoft Windows 11 Version 25H2AffectedFixed in
- < 10.0.26200.7171
- 10.0.26200.7171
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.8027
- 10.0.17763.8027
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.8027
- 10.0.17763.8027
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.4405
- 10.0.20348.4405
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64AffectedFixed in
- < 10.0.25398.1965
- 10.0.25398.1965
- Microsoft Windows Server 2025x64AffectedFixed in
- < 10.0.26100.7171
- 10.0.26100.7171
- Microsoft Windows Server 2025 (Server Core installation)x64AffectedFixed in
- < 10.0.26100.7171
- 10.0.26100.7171
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 180932-bit, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H3ARM64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows 11 Version 24H2ARM64, x64 |
|
|
| Microsoft Windows 11 Version 25H2 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2025x64 |
|
|
| Microsoft Windows Server 2025 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1809: 10.0.17763.8027
- Microsoft Windows 10 Version 21H2: 10.0.19044.6575
- Microsoft Windows 10 Version 22H2: 10.0.19045.6575
- Microsoft Windows 11 version 22H3: 10.0.22631.6199
- Microsoft Windows 11 Version 23H2: 10.0.22631.6199
- Microsoft Windows 11 Version 24H2: 10.0.26100.7171
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-62215
- CISA's deadline for US federal agencies: 2025-12-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each affected Windows system to the fixed build listed for its version.
- Prioritize systems where many users log on, such as servers and shared workstations, since the attacker needs local access.
- Verify the installed build numbers after patching to confirm every system reached a fixed version.
- Limit local and interactive logon rights to the users who need them.
- Check systems for signs of compromise, such as unexpected privileged accounts or processes, given known exploitation.
- Follow the Microsoft advisory and CISA's required action; U.S. federal agencies must remediate by 2025-12-03.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), CWE-415 Double Free
Questions about CVE-2025-62215
- Is CVE-2025-62215 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-11-12. Whether it is used in ransomware campaigns is unknown.
- Can it be exploited remotely?
- No. The attack vector is local, and the attacker needs an authorized account with low privileges. It is used to elevate privileges on a system the attacker can already access.
- How do I know a system is fixed?
- Compare the Windows build number with the fixed version for that release, for example
10.0.26100.7171for Windows 11 Version 24H2 and Windows Server 2025, or10.0.20348.4405for Windows Server 2022.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.