cve.bz

CVE-2025-62215 Microsoft Windows Race Condition Vulnerability

7.0 highKEVExploitEPSS 4.5%

High (7.0) in Microsoft Windows. In CISA KEV since 2025-11-12. EPSS 4.5% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
4.5% (unchanged from 4.5% a week ago; 4.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 92nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2025-11-12, due 2025-12-03
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
CWE-415 Double Free
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-62215 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-62215?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-62215?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-62215 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.8027
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.6575
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.6575
Microsoft Windows 11 version 22H3from 10.0.22631.0 before 10.0.22631.6199
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.6199
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.7171
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.7171
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.8027
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.8027
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.4405
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)from 10.0.25398.0 before 10.0.25398.1965
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.7171
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.7171

Public exploits

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

2 more

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON