# CVE-2025-62215: Microsoft Windows Race Condition

> A race condition in the Windows Kernel allows an authorized local attacker to elevate privileges.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 12 Nov 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-hr5f-g8f8-p354

## What is CVE-2025-62215?

CVE-2025-62215 is a high-severity vulnerability in Microsoft Windows 10 1809, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.

Weakness: CWE-415 (Double Free), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2025-62215?

It affects 10 products.


Products: Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-62215?

No fix has been published for CVE-2025-62215 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Dec 2025.

## Is CVE-2025-62215 being exploited?

Yes. Attackers have exploited CVE-2025-62215 in the wild since at least 12 Nov 2025.

Public exploit code:

- This PoC demonstrates a race condition in the Windows kernel leading to a double-free vulnerability, allowing local privilege escalation to SYSTEM. The exploit uses multithreaded handle manipulation and heap spraying to trigger the flaw under controlled conditions. (github_poc): https://github.com/abrewer251/CVE-2025-62215_Windows_Kernel_PE
- https://github.com/gowonisgood/CVE-2025-62215-POC (github_poc): https://github.com/gowonisgood/CVE-2025-62215-POC
- Hands‑on analysis of CVE‑2025‑62215, a Windows Kernel race condition exploited in the wild. Demonstrates privilege escalation to SYSTEM, detection scripts, and patch validation strategies for enterprise defenders and red teamers. (github_poc): https://github.com/mrk336/Kernel-Chaos-Weaponizing-CVE-2025-62215-for-SYSTEM-Privilege-Escalation
- CVE-2025-62215: Windows Kernel Race Condition + Double-Free EoP (github_poc): https://github.com/theman001/CVE-2025-62215
- CVE-2025-62215 is an Elevation of Privilege (EoP) vulnerability in the Windows Kernel, disclosed in November 2025 and confirmed to be actively exploited as a zero-day. (github_poc): https://github.com/nullxall/cve-2025-62215-exploit-poc
- CVE-2025-62215 exploit development using Claude Code Agent Team (github_poc): https://github.com/uky007/CVE-2025-62215_analysis

## Other vulnerabilities in Microsoft Windows 10 1809

- [CVE-2024-29988](https://insights.sbomify.com/CVE-2024-29988/): Microsoft SmartScreen Prompt Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2024-21412](https://insights.sbomify.com/CVE-2024-21412/): Microsoft Windows Internet Shortcut Files Security Feature Bypass (high 8.1, exploited in the wild)
- [CVE-2025-62221](https://insights.sbomify.com/CVE-2025-62221/): Microsoft Windows Use After Free (high 7.8, exploited in the wild)
- [CVE-2025-30400](https://insights.sbomify.com/CVE-2025-30400/): Microsoft Windows DWM Core Library Use-After-Free (high 7.8, exploited in the wild)
- [CVE-2024-21338](https://insights.sbomify.com/CVE-2024-21338/): Microsoft Windows Kernel Exposed IOCTL with Insufficient Access Control (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62215 and fix it if it is affected.

What it is: CVE-2025-62215 is a high-severity vulnerability in Microsoft Windows 10 1809, published on 11 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-62215 in the wild since at least 12 Nov 2025.

Affected product: Microsoft Windows 10 1809. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62215/ (Markdown: https://insights.sbomify.com/CVE-2025-62215/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62215
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62215
- OSV: https://osv.dev/vulnerability/CVE-2025-62215

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62215/
Summaries are generated and may contain mistakes; the official description above is the record.