CVE-2025-24993: Microsoft Windows NTFS Heap-Based Buffer Overflow
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-03-11.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 2.2%
- higher than 83% of all CVEs
- Added to CISA KEV
- 2025-03-11
- US federal due date 2025-04-01
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-24993 explained
CVE-2025-24993 is a heap-based buffer overflow (CWE-122) in the NTFS component of Microsoft Windows. It lets an unauthorized attacker execute code locally. CISA lists it as a known exploited vulnerability, so attackers are known to use it, and patching affected Windows client and server systems should be a priority.
Impact
A successful attacker can run code on the affected system with high impact on confidentiality, integrity and availability. CISA rates the technical impact as total. The attack is local, needs no privileges and has low complexity, but requires user interaction. CISA assesses it as not automatable, so mass exploitation without manual steps is less likely. Attackers are known to exploit it. Ransomware use is listed as unknown.
Who is affected
The CVE record lists Windows 10 Versions 1507, 1607, 1809, 21H2 and 22H2, Windows 11 versions 22H2, 22H3, 23H2 and 24H2, Windows Server 2008 R2 Service Pack 1 (including Server Core) and Windows Server 2008 Service Pack 2. Fixed builds include 10.0.10240.20947, 10.0.14393.7876, 10.0.17763.7009, 10.0.19044.5608, 10.0.19045.5608, 10.0.22621.5039, 10.0.22631.5039, 10.0.26100.3476, 6.1.7601.27618 and 6.0.6003.23168. Further products are listed on this page.
Written with AI from the data on this page and checked against it automatically.
Official description
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code locally.
CISA 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.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.20947
- 10.0.10240.20947
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.7876
- 10.0.14393.7876
- Microsoft Windows 10 Version 180932-bit, x64AffectedFixed in
- < 10.0.17763.7009
- 10.0.17763.7009
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.5608
- 10.0.19044.5608
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.5608
- 10.0.19045.5608
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.5039
- 10.0.22621.5039
- Microsoft Windows 11 version 22H3ARM64AffectedFixed in
- < 10.0.22631.5039
- 10.0.22631.5039
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.5039
- 10.0.22631.5039
- Microsoft Windows 11 Version 24H2ARM64, x64AffectedFixed in
- < 10.0.26100.3476
- 10.0.26100.3476
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.27618
- 6.1.7601.27618
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H3ARM64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows 11 Version 24H2ARM64, x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
Show 15 more products
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.27618
- 6.1.7601.27618
- Microsoft Windows Server 2008 Service Pack 232-bit, x64AffectedFixed in
- < 6.0.6003.23168
- 6.0.6003.23168
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64AffectedFixed in
- < 6.0.6003.23168
- 6.0.6003.23168
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.25368
- 6.2.9200.25368
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.25368
- 6.2.9200.25368
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.22470
- 6.3.9600.22470
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.22470
- 6.3.9600.22470
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.7876
- 10.0.14393.7876
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.7876
- 10.0.14393.7876
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.7009
- 10.0.17763.7009
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.7009
- 10.0.17763.7009
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.3328
- 10.0.20348.3328
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64AffectedFixed in
- < 10.0.25398.1486
- 10.0.25398.1486
- Microsoft Windows Server 2025x64AffectedFixed in
- < 10.0.26100.3476
- 10.0.26100.3476
- Microsoft Windows Server 2025 (Server Core installation)x64AffectedFixed in
- < 10.0.26100.3476
- 10.0.26100.3476
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 232-bit, x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2025x64 |
|
|
| Microsoft Windows Server 2025 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.20947
- Microsoft Windows 10 Version 1607: 10.0.14393.7876
- Microsoft Windows 10 Version 1809: 10.0.17763.7009
- Microsoft Windows 10 Version 21H2: 10.0.19044.5608
- Microsoft Windows 10 Version 22H2: 10.0.19045.5608
- Microsoft Windows 11 version 22H2: 10.0.22621.5039
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24993
- CISA's deadline for US federal agencies: 2025-04-01 (passed) – a useful benchmark for everyone else, too.
What to do
- Install Microsoft's security update so each system reaches the fixed build listed for its Windows version.
- Prioritize patching because CISA lists this vulnerability as known exploited; US federal agencies had a due date of 2025-04-01.
- Follow the Microsoft advisory for mitigations on systems that cannot be updated promptly.
- Train users to avoid opening untrusted files or media, since exploitation requires user interaction.
- Check affected systems for signs of compromise, especially those that remained unpatched.
- Discontinue use of systems where mitigations are unavailable, as CISA's required action states.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-122 Heap-based Buffer Overflow
Questions about CVE-2025-24993
- Is CVE-2025-24993 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-03-11, meaning attackers are known to use it. Whether it is used in ransomware campaigns is listed as unknown.
- Can it be exploited remotely?
- The CVSS attack vector is local, and user interaction is required. No privileges are needed. CISA rates it as not automatable, but the technical impact as total.
- Which update fixes it?
- Each affected Windows version has a fixed build in the CVE record, for example
10.0.19045.5608for Windows 10 Version 22H2 and10.0.26100.3476for Windows 11 Version 24H2. Apply Microsoft's update to reach these builds.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.