dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Apr 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-24991

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.10240.20947 / 10.0.14393.7876 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds read in Windows NTFS allows an authorized attacker to disclose information locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An out-of-bounds read vulnerability exists in Windows NTFS (the Windows NT File System) that allows a locally authenticated, authorized attacker to read memory contents beyond intended buffer boundaries, leading to disclosure of sensitive information.

MitigationApply the Microsoft security update for CVE-2025-24991 when released; this is a Windows kernel-level file system vulnerability that requires vendor-provided patches rather than configuration changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20947
Windows 10 1607Operating system
Affected:< 10.0.14393.7876
Windows 10 1809Operating system
Affected:< 10.0.17763.7009
Windows 10 21h2Operating system
Affected:< 10.0.19044.5608
Windows 10 22h2Operating system
Affected:< 10.0.19045.5608
Windows 11 22h2Operating system
Affected:< 10.0.22621.5039
Windows 11 23h2Operating system
Affected:< 10.0.22631.5039
Windows 11 24h2Operating system
Affected:< 10.0.26100.3403

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Open Command Prompt and run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`. Alternatively, check the registry key `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion` for the `CurrentBuild` and `DisplayVersion` values.
    Affected if The displayed build number is lower than the threshold for your specific Windows release: 1507 requires 10240.20947 or higher, 1607 requires 14393.7876 or higher, 1809 requires 17763.7009 or higher, 21h2 requires 19044.5608 or higher, 22h2 requires 19045.5608 or higher, 11 22h2 requires 22621.5039 o
  2. Verify NTFS filesystem is in use
    Open Command Prompt and run `fsutil fsinfo volumeinfo C:` (replace C: with any drive letter). Look for the line showing 'File System Name : NTFS'.
    Affected if The volume is formatted with NTFS, as the vulnerability exists in the Windows NTFS driver.
  3. Check NTFS.sys driver version
    Right-click the file `%SystemRoot%\System32\drivers\NTFS.sys`, select Properties, and view the Details tab for the File Version. Alternatively, run `powershell -command "(Get-Item 'C:\Windows\System32\drivers\NTFS.sys').VersionInfo.FileVersion"`.
    Affected if The NTFS.sys driver version is older than the version corresponding to your Windows build's patch level, indicating the security update has not been applied.
  4. Confirm security update is installed
    Open Settings > Windows Update > Update history, or run `powershell -command "Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20"` to list recently installed updates.
    Affected if The specific KB update addressing CVE-2025-24991 is not listed among installed updates.

Your environment is affected if the Windows build number or NTFS driver version is below the affected thresholds AND the volume uses NTFS, meaning the system is missing the security update that patches the NTFS driver.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20947 / 10.0.14393.7876 / 10.0.17763.7009 or later
Fixed in 10.0.10240.2094710.0.14393.787610.0.17763.7009
Interim mitigation

Apply the Microsoft security update for CVE-2025-24991 when released; this is a Windows kernel-level file system vulnerability that requires vendor-provided patches rather than configuration changes.

Recommended fix High confidence

March 2025 Windows Security Updates - Install the appropriate cumulative update for your Windows version: Windows 10 1507 (build 10.0.10240.20947+), Windows 10 1607 (build 10.0.14393.7876+), Windows 10 1809 (build 10.0.17763.7009+), Windows 10 21h2 (build 10.0.19044.5608+), Windows 10 22h2 (build 10

  1. Open Windows Settings on the affected system
  2. Navigate to Windows Update (Settings > Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install the latest cumulative security update
  4. Alternatively, manually download the appropriate security update from the Microsoft Update Catalog for your specific Windows version and build number
  5. Restart the system after the update is installed to ensure the NTFS vulnerability is remediated
  6. Verify the installed update by checking the Windows update history - the KB number should correspond to the March 2025 security update (or later)
Caveat Standard Windows cumulative security update with no expected breaking changes; as with any system update, test in a non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24991 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24991 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data