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

Microsoft Windows vulnerability

Microsoft Windows NTFS contains an out-of-bounds read vulnerability allowing authorized attackers to disclose information locally.

Verdict

Today item — known-exploited.

An out-of-bounds read in Windows NTFS enables local information disclosure by authenticated users. Active exploitation in the wild indicates practical threat despite low EPSS score. Mitigation requires system patching.

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

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
5 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.01852 — 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-125 Out-of-bounds Read — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-125 · Out-of-bounds ReadMemory safety
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 authenticate to a Windows system with standard user privileges.
Business
Legitimate user accounts become vectors for unauthorized data access within the organization.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft a malformed NTFS request that reads memory beyond allocated boundaries.
Business
Sensitive data from kernel memory or other processes becomes accessible to unprivileged accounts.
3

Lateral reach — past segmentation narrative 3

Attacker
I extract confidential information such as encryption keys, credentials, or system secrets from the leaked memory.
Business
Compromised credentials and secrets enable lateral movement and further system compromise.
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)
  • 5 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.