Threats / Microsoft / CVE-2025-62215
CVE-2025-62215
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
Microsoft Windows Kernel race condition (CWE-362) allows local attackers with low privileges to escalate to SYSTEM level. Actively exploited in the wild.
Verdict
Today item — known-exploited.
A race condition in the Windows Kernel enables privilege escalation from low-privilege local access to SYSTEM. The vulnerability is being actively exploited. Patch immediately on affected systems.
CISA KEV Yes · 2025-11-125EPSS 0.06073 (verify live)6Exploit Public PoC7CVSS 73CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-11-12).
Probability (EPSS)
EPSS 0.06073 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7 (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) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-362 Race Condition, CWE-415 Double Free — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain initial local access to a Windows system with standard user privileges.
Business
An attacker establishes a foothold on the endpoint, bypassing perimeter controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I identify and trigger a race condition in the Windows Kernel to escalate my privileges to SYSTEM level.
Business
The attacker gains unrestricted control of the compromised system, enabling lateral movement and persistence.
3
Lateral reach — past segmentation narrative 3
Attacker
With SYSTEM access, I can install malware, modify system files, and maintain persistent backdoor access.
Business
Critical infrastructure and sensitive data become vulnerable to theft, manipulation, or destruction.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05