Buffer overflow in Microsoft Windows 10 Version 1507
CVE-2025-24993
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code locally.
Vulnerability class: Buffer Overflow
EPSS: 0.032 (87.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C.
Affected products
- Microsoft Windows 10 Version 1507 — versions 10.0.10240.0
- Microsoft Windows 10 Version 1607 — versions 10.0.14393.0
- Microsoft Windows 10 Version 1809 — versions 10.0.17763.0
- Microsoft Windows 10 Version 21h2 — versions 10.0.19044.0
- Microsoft Windows 10 Version 22h2 — versions 10.0.19045.0
- Microsoft Windows 11 Version 22h2 — versions 10.0.22621.0
- Microsoft Windows 11 Version 22h3 — versions 10.0.22631.0
- Microsoft Windows 11 Version 23h2 — versions 10.0.22631.0
- Microsoft Windows 11 Version 24h2 — versions 10.0.26100.0
- Microsoft Windows Server 2008 R2 Service Pack 1 — versions 6.1.7601.0
Weakness classification (CWE)
CISA KEV (Known Exploited Vulnerabilities)
This CVE is on the CISA KEV catalog, added on . CISA KEV inclusion means CISA has confirmed in-the-wild exploitation; US federal agencies are required to remediate within a published due date.
BOD 22-01 due date: .
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Public proof-of-concept exploits
References
- Windows NTFS Remote Code Execution Vulnerability (vendor-advisory, patch)
Frequently asked questions
- What is CVE-2025-24993?
- CVE-2025-24993 is a high-severity vulnerability in Microsoft Windows 10 Version 1507, classified under Heap-based Buffer Overflow. CVSS score: 7.8/10. Published 2025-03-11.
- How severe is CVE-2025-24993?
- High severity. CVSS v3 base score is 7.8 out of 10.
- Is CVE-2025-24993 known to be exploited?
- Yes. CVE-2025-24993 is listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-11), indicating it is being actively exploited. 3 public proof-of-concept repositories are indexed.