CVE-2025-24993Exploited in the wildNVD status: Analyzed
Microsoft Windows NTFS Heap-Based Buffer Overflow
CVE-2025-24993 is a high-severity heap-based buffer overflow vulnerability in Windows 10 Version 1507 from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 10.0.10240.20947 as the first without the flaw, so updating Windows 10 Version 1507 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on March 11, 2025, which means attacks have been observed in the wild.
Patch now
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Windows 10 Version 1507 to 10.0.10240.20947 or a later version.
- Update Windows 10 Version 1607 to 10.0.14393.7876 or a later version.
- Update Windows 10 Version 1809 to 10.0.17763.7009 or a later version.
- CISA's 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.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 10 Version 1507 | 10.0.10240.0 up to, but not including, 10.0.10240.20947 | 10.0.10240.20947 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.7876 | 10.0.14393.7876 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.7009 | 10.0.17763.7009 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.5608 | 10.0.19044.5608 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.5608 | 10.0.19045.5608 |
| Microsoft | Windows 11 version 22H2 | 10.0.22621.0 up to, but not including, 10.0.22621.5039 | 10.0.22621.5039 |
| Microsoft | Windows 11 version 22H3 | 10.0.22631.0 up to, but not including, 10.0.22631.5039 | 10.0.22631.5039 |
| Microsoft | Windows 11 Version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.5039 | 10.0.22631.5039 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.3476 | 10.0.26100.3476 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 | 6.1.7601.0 up to, but not including, 6.1.7601.27618 | 6.1.7601.27618 |
| Microsoft | Windows Server 2008 R2 Service Pack 1 (Server Core installation) | 6.1.7601.0 up to, but not including, 6.1.7601.27618 | 6.1.7601.27618 |
| Microsoft | Windows Server 2008 Service Pack 2 | 6.0.6003.0 up to, but not including, 6.0.6003.23168 | 6.0.6003.23168 |
| Microsoft | Windows Server 2008 Service Pack 2 (Server Core installation) | 6.0.6003.0 up to, but not including, 6.0.6003.23168 | 6.0.6003.23168 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.25368 | 6.2.9200.25368 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.25368 | 6.2.9200.25368 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.22470 | 6.3.9600.22470 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.22470 | 6.3.9600.22470 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.7876 | 10.0.14393.7876 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.7876 | 10.0.14393.7876 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.7009 | 10.0.17763.7009 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.7009 | 10.0.17763.7009 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.3328 | 10.0.20348.3328 |
| Microsoft | Windows Server 2022, 23H2 Edition (Server Core installation) | 10.0.25398.0 up to, but not including, 10.0.25398.1486 | 10.0.25398.1486 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.3476 | 10.0.26100.3476 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.3476 | 10.0.26100.3476 |
Version data comes from the organisation that assigned the CVE; 10 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code locally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24993US Government Resource
Other vulnerabilities in Windows 10 Version 1507
- 7.0 High severity
- 7.8 High severity
- 7.0 High severity
- 7.7 High severity
- 7.0 High severity
Recent Heap-based Buffer Overflow vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 8.2 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.