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

Microsoft Windows vulnerability

Microsoft Windows NTFS contains a heap-based buffer overflow vulnerability allowing local code execution. The flaw has been exploited in the wild.

Verdict

Today item — known-exploited.

A locally exploitable heap overflow in Windows NTFS enables arbitrary code execution with active real-world exploitation. Organizations should prioritize patching to prevent privilege escalation and system compromise.

CISA KEV Yes · 2025-03-113EPSS 0.02092 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
6 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-03-11).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.02092 — 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-122 Heap-based Buffer Overflow — weakness family: Memory safety.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 craft a malicious file or filesystem operation that triggers improper bounds checking in NTFS heap memory.
Business
An attacker gains initial foothold on Windows systems through local exploitation vectors.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I overflow the heap buffer to overwrite adjacent memory structures and redirect execution flow to my payload.
Business
Arbitrary code execution occurs within the NTFS driver context, potentially with elevated privileges.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute system commands or install persistence mechanisms with the privileges obtained from the overflow.
Business
Attackers establish durable access, escalate privileges, or move laterally across the network.
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)
  • 6 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.