Skip to content
Server Security Center
KEVmedium5.5

CVE-2025-24991: Microsoft Windows NTFS Out-Of-Bounds Read

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-03-11.

CVSS v3.1 (CVE record)
5.5
medium
EPSS (exploit probability, 30 days)
2.0%
higher than 81.4% of all CVEs
Added to CISA KEV
2025-03-11
US federal due date 2025-04-01
Automatable (CISA SSVC)
no
technical impact: partial

CVE-2025-24991 explained

CVE-2025-24991 is an out-of-bounds read in the NTFS file system component of Microsoft Windows. It lets an authorized attacker disclose information locally. CISA lists it in its Known Exploited Vulnerabilities catalog, so attackers are known to use it, and it affects a wide range of Windows client and server versions.

Impact

An attacker with local access can read memory they should not reach and disclose information. The CVSS vector shows a local attack with low complexity and no privileges required, but user interaction is required. Confidentiality impact is high, with no integrity or availability impact. CISA rates it as not automatable, with partial technical impact. CISA reports active exploitation; ransomware use is 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, and Windows Server 2008 SP2 and 2008 R2 SP1, including Server Core. 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

Out-of-bounds read in Windows NTFS allows an authorized attacker to disclose information 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, x64
    Affected
    • < 10.0.10240.20947
    Fixed in
    • 10.0.10240.20947
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5608
    Fixed in
    • 10.0.19044.5608
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5608
    Fixed in
    • 10.0.19045.5608
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.5039
    Fixed in
    • 10.0.22621.5039
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.5039
    Fixed in
    • 10.0.22631.5039
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.5039
    Fixed in
    • 10.0.22631.5039
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27618
    Fixed in
    • 6.1.7601.27618
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27618
    Fixed in
    • 6.1.7601.27618
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23168
    Fixed in
    • 6.0.6003.23168
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23168
    Fixed in
    • 6.0.6003.23168
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25368
    Fixed in
    • 6.2.9200.25368
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25368
    Fixed in
    • 6.2.9200.25368
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22470
    Fixed in
    • 6.3.9600.22470
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22470
    Fixed in
    • 6.3.9600.22470
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3328
    Fixed in
    • 10.0.20348.3328
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1486
    Fixed in
    • 10.0.25398.1486
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476

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
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24991
  • CISA's deadline for US federal agencies: 2025-04-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security update so each system reaches the fixed build listed for its Windows version.
  2. Prioritize patching because CISA lists this vulnerability as known exploited; US federal agencies had a due date of 2025-04-01.
  3. Follow the Microsoft advisory and apply any mitigations it describes for systems that cannot be updated promptly.
  4. Limit local and interactive access to systems and train users to be cautious, since exploitation requires user interaction.
  5. Review systems for signs of compromise, especially those that remained unpatched after 2025-03-11.

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
Partial – limited control or information

Weakness: CWE-125 Out-of-bounds Read

Questions about CVE-2025-24991

Is CVE-2025-24991 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-03-11. Whether it has been used in ransomware campaigns is listed as unknown.
Can it be exploited remotely?
The CVSS vector lists a local attack vector and requires user interaction. The impact is information disclosure; there is no integrity or availability impact.
Which update fixes it?
Each affected Windows version has its own fixed build in the CVE record, for example 10.0.19045.5608 for Windows 10 Version 22H2 and 10.0.26100.3476 for Windows 11 Version 24H2.

Written with AI from the data on this page and checked against it automatically.

References

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.