dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-25175

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 elevate privileges 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 the Windows NTFS filesystem driver. The flaw allows a local authenticated attacker to read unintended memory contents, which can be leveraged to elevate privileges to higher integrity levels or gain SYSTEM access on the affected Windows system.

MitigationApply the relevant Microsoft security update for this vulnerability once released. Until a patch is available, restrict local non-administrative user access and monitor for suspicious filesystem activity.

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 1607Operating system
Affected:< 10.0.14393.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8957
Windows Server 2019Operating system
Affected:< 10.0.17763.8511

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"Version"' to get the exact Windows version and build number
    Affected if The version and build number fall within the affected ranges: Windows 10 1607 < 14393.8957, 1809 < 17763.8511, 21h2 < 19044.7058, 22h2 < 19045.7058; Windows 11 23h2 < 22631.6783; Windows Server 2016 < 14393.8957; Server 2019 < 17763.8511; or any Server 2012/R2 version
  2. Verify NTFS driver is in use
    Check that the system uses NTFS filesystem by running 'fsutil fsinfo volumeinfo C:' and confirming 'File System Name : NTFS'
    Affected if The filesystem is NTFS (which is the default for most Windows installations)
  3. Confirm driver file version
    Locate ntfs.sys in System32\drivers\ folder and check its version properties. Run 'dir %WINDIR%\System32\drivers\ntfs.sys' to see version info, or use 'powershell (Get-Item C:\Windows\System32\drivers\ntfs.sys).VersionInfo'
    Affected if The ntfs.sys version is lower than the fixed versions corresponding to the Windows build (this confirms the vulnerable driver is loaded)

A system is affected if it runs any Windows version listed in the affected products range AND uses the NTFS filesystem with an unpatched ntfs.sys driver version.

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.14393.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply the relevant Microsoft security update for this vulnerability once released. Until a patch is available, restrict local non-administrative user access and monitor for suspicious filesystem activity.

Recommended fix High confidence

Install the appropriate Windows security update containing the fix. Specific KB articles should be obtained from catalog.update.microsoft.com - fixed versions are: Windows 10 1607: 10.0.14393.8957, Windows 10 1809: 10.0.17763.8511, Windows 10 21h2: 10.0.19044.7058, Windows 10 22h2: 10.0.19045.7058,

  1. Open Settings on the affected Windows system and navigate to Windows Update
  2. Click 'Check for updates' and install all available security updates
  3. Alternatively, manually download and install the specific KB patch from the Microsoft Update Catalog corresponding to your Windows version
  4. For Windows Server systems, use Windows Server Update Services (WSUS) or manually apply the relevant security update
  5. Restart the system after installing the update
  6. Verify the installed KB patch matches or exceeds the fixed version number for your Windows release
Caveat Windows Server 2012 and Windows Server 2012 R2 have no fix available as they are end-of-life; migration to supported OS required

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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