Threats / Microsoft / CVE-2024-38106
CVE-2024-38106
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
Microsoft Windows Kernel privilege escalation vulnerability exploitable via race condition, allowing local attackers to gain SYSTEM privileges. Actively exploited in the wild.
Verdict
Today item — known-exploited.
A local privilege escalation flaw in Windows Kernel requiring race condition exploitation. Active exploitation in the wild poses significant risk to unpatched systems, particularly those with untrusted local user access or compromised application contexts.
CISA KEV Yes · 2024-08-135EPSS 0.06337 (verify live)6CVSS 73CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
11 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 2024-08-13).
Probability (EPSS)
EPSS 0.06337 — 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-591 CWE-591.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 the same day 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.
WeaknessCWE-591 · CWE-591
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 execute code with limited local privileges on a target Windows system.
Business
Attacker gains foothold through compromised application, weak credential, or supply chain vector.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger the race condition in the Windows Kernel to escalate my privileges to SYSTEM level.
Business
Attacker obtains highest system privileges, bypassing access controls and security boundaries.
3
Lateral reach — past segmentation narrative 3
Attacker
I install persistence mechanisms, disable security tools, and move laterally across the network.
Business
Complete system compromise enables data theft, malware deployment, lateral movement, and operational disruption.
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