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-24993

HIGH · 7.8 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
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code 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

Heap-based buffer overflow vulnerability in the Windows NTFS driver allows a local attacker to execute arbitrary code by exploiting improper bounds checking when handling NTFS filesystem operations.

MitigationApply Microsoft security updates for Windows when released; restrict local access to trusted users and monitor for privilege escalation attempts.

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
High
Availability
High

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

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 the Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build number
    Affected if The version and build number fall below any of the listed thresholds (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, or 10.0.26100.3403)
  2. Confirm NTFS filesystem is in use
    Run 'fsutil fsinfo volumeinfo C:' (or any local drive letter) to verify the filesystem type is NTFS
    Affected if The target drive uses NTFS, as the vulnerability exists in the NTFS.sys driver
  3. Check for the security update
    Run 'wmic qfe list' or check Windows Update history for installation of the CVE-2025-24993 patch (typically included in a March 2025 or later security update)
    Affected if The security update for CVE-2025-24993 is not installed or the installation date predates the patch release
  4. Verify NTFS.sys driver version
    Run 'driverquery /v | findstr NTFS' to display the NTFS.sys driver version, then compare against the version bundled with the patched OS builds
    Affected if The NTFS.sys driver version is older than the version included in the patched builds for your Windows version

The system is affected if it runs a Windows 10 or 11 version below the specified build thresholds AND uses NTFS filesystem AND lacks the CVE-2025-24993 security update.

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 Microsoft security updates for Windows when released; restrict local access to trusted users and monitor for privilege escalation attempts.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20947 | Windows 10 1607: 10.0.14393.7876 | Windows 10 1809: 10.0.17763.7009 | Windows 10 21h2: 10.0.19044.5608 | Windows 10 22h2: 10.0.19045.5608 | Windows 11 22h2: 10.0.22621.5039 | Windows 11 23h2: 10.0.22631.5039 | Windows 11 24h2: 10.0.26100.3403

  1. Open Windows Settings by pressing Win + I
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install all available security updates
  4. If updates are available, ensure the security update containing the fix for CVE-2025-24993 is installed
  5. Restart the system when prompted to complete the installation
  6. Verify the update was installed by checking Windows Update history
Caveat Standard Windows update risks—ensure backups exist before applying updates in enterprise environments

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24993 — 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-24993 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