basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2024-38106
CVE-2024-38106 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-133EPSS 0.06337 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
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
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-591 CWE-591.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 11 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.