Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.
CVE-2025-62215
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-11-12), indicating real-world exploitation has been confirmed by US federal agencies. a secondary CVSS source baseline 7.0 retained for reference (NVD's own analysis pending). Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.0
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 92.6%
- KEV
- ⚠ Exploited
Published
November 11, 2025
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jun 11, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-62215Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-62215Vendor Advisories for CVE-2025-62215(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 78× in last 7d / 392× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 732 total refreshes for this CVE.
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:00 UTCEG score recompute
- 2026-07-22 23:10 UTCEG score recompute
- 2026-07-22 23:10 UTCVendor advisory
- 2026-07-22 23:10 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:14 UTCGHSA enrichment
- 2026-07-22 15:18 UTCEG score recompute
- 2026-07-22 15:18 UTCVendor advisory
- 2026-07-22 15:18 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 11:22 UTCVendor advisory
- 2026-07-22 11:22 UTCGHSA enrichment
- 2026-07-22 07:27 UTCVendor advisory
- 2026-07-22 07:26 UTCGHSA enrichment
- 2026-07-22 03:31 UTCVendor advisory
- 2026-07-22 03:30 UTCGHSA enrichment
- 2026-07-21 23:33 UTCVendor advisory
- 2026-07-21 23:33 UTCGHSA enrichment
- 2026-07-21 19:37 UTCVendor advisory
- 2026-07-21 19:37 UTCGHSA enrichment
- 2026-07-21 15:40 UTCEG score recompute
Show 75 moreShow fewer
- 2026-07-21 15:40 UTCVendor advisory
- 2026-07-21 15:40 UTCGHSA enrichment
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 11:44 UTCVendor advisory
- 2026-07-21 11:44 UTCGHSA enrichment
- 2026-07-21 07:47 UTCVendor advisory
- 2026-07-21 07:47 UTCGHSA enrichment
- 2026-07-21 03:52 UTCVendor advisory
- 2026-07-21 03:52 UTCGHSA enrichment
- 2026-07-20 23:56 UTCVendor advisory
- 2026-07-20 23:56 UTCGHSA enrichment
- 2026-07-20 20:00 UTCEG score recompute
- 2026-07-20 20:00 UTCVendor advisory
- 2026-07-20 20:00 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 16:04 UTCGHSA enrichment
- 2026-07-20 12:07 UTCGHSA enrichment
- 2026-07-20 08:11 UTCVendor advisory
- 2026-07-20 08:11 UTCGHSA enrichment
- 2026-07-20 04:15 UTCVendor advisory
- 2026-07-20 04:15 UTCGHSA enrichment
- 2026-07-20 00:19 UTCVendor advisory
- 2026-07-20 00:19 UTCGHSA enrichment
- 2026-07-19 20:22 UTCVendor advisory
- 2026-07-19 20:22 UTCGHSA enrichment
- 2026-07-19 16:26 UTCEG score recompute
- 2026-07-19 16:26 UTCVendor advisory
- 2026-07-19 16:26 UTCGHSA enrichment
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 12:30 UTCVendor advisory
- 2026-07-19 12:29 UTCGHSA enrichment
- 2026-07-19 08:32 UTCVendor advisory
- 2026-07-19 08:32 UTCGHSA enrichment
- 2026-07-19 04:35 UTCEG score recompute
- 2026-07-19 04:35 UTCVendor advisory
- 2026-07-19 04:35 UTCGHSA enrichment
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 00:38 UTCGHSA enrichment
- 2026-07-18 20:42 UTCVendor advisory
- 2026-07-18 20:42 UTCGHSA enrichment
- 2026-07-18 16:46 UTCVendor advisory
- 2026-07-18 16:46 UTCGHSA enrichment
- 2026-07-18 12:50 UTCEG score recompute
- 2026-07-18 12:50 UTCVendor advisory
- 2026-07-18 12:50 UTCGHSA enrichment
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 08:53 UTCVendor advisory
- 2026-07-18 08:53 UTCGHSA enrichment
- 2026-07-18 04:57 UTCVendor advisory
- 2026-07-18 04:57 UTCGHSA enrichment
- 2026-07-18 01:01 UTCVendor advisory
- 2026-07-18 01:01 UTCGHSA enrichment
- 2026-07-17 21:05 UTCVendor advisory
- 2026-07-17 21:05 UTCGHSA enrichment
- 2026-07-17 17:09 UTCVendor advisory
- 2026-07-17 17:08 UTCGHSA enrichment
- 2026-07-17 13:13 UTCVendor advisory
- 2026-07-17 13:13 UTCGHSA enrichment
- 2026-07-17 09:16 UTCEG score recompute
- 2026-07-17 09:16 UTCVendor advisory
- 2026-07-17 09:16 UTCGHSA enrichment
- 2026-07-17 05:20 UTCVendor advisory
- 2026-07-17 05:20 UTCGHSA enrichment
- 2026-07-17 01:24 UTCVendor advisory
- 2026-07-17 01:24 UTCGHSA enrichment
- 2026-07-16 21:29 UTCVendor advisory
- 2026-07-16 21:29 UTCGHSA enrichment
- 2026-07-16 17:33 UTCVendor advisory
- 2026-07-16 17:33 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 13:36 UTCVendor advisory
Publicly available exploits
(6 references)Working exploit code is in the public domain (5 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-52494First seen Apr 6, 2026
Windows Kernel - Elevation of Privilege
Open source ↗ - Open source ↗GitHub PoCgowonisgood/CVE-2025-62215-POCFirst seen Mar 2, 2026
- GitHub PoCtheman001/CVE-2025-62215First seen Dec 23, 2025
CVE-2025-62215: Windows Kernel Race Condition + Double-Free EoP
Open source ↗ - GitHub PoCabrewer251/CVE-2025-62215_Windows_Kernel_PEFirst seen Nov 18, 2025
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.
Open source ↗ - GitHub PoCmrk336/Kernel-Chaos-Weaponizing-CVE-2025-62215-for-SYSTEM-Privilege-EscalationFirst seen Nov 18, 2025
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.
Open source ↗ - GitHub PoCdexterm300/CVE-2025-62215-exploit-pocFirst seen Nov 14, 2025
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.
Open source ↗
Frequently asked(6)
What is CVE-2025-62215?
When was CVE-2025-62215 disclosed?
Is CVE-2025-62215 actively exploited?
What is the CVSS score of CVE-2025-62215?
Which products are affected by CVE-2025-62215?
How do I remediate CVE-2025-62215?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-62215
Is Your Infrastructure Affected by CVE-2025-62215?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.