dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-49678

HIGH · 7.0 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Null pointer dereference 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

This is a local privilege escalation vulnerability in Windows NTFS (the NT File System driver). The vulnerability is a null pointer dereference flaw that allows an authenticated local attacker to elevate their privileges to higher privilege levels. The attacker requires some level of authorized access to the system but can exploit this flaw to gain administrative or SYSTEM-level privileges.

MitigationApply Microsoft security updates for Windows NTFS as they become available through standard Windows Update or patch management deployment. Verify that endpoint protection and least-privilege configurations are in place to limit local attack surface.

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.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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

CVSS:3.1/AV:L/AC:H/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 build version
    Open Command Prompt or PowerShell and run 'winver' or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number
    Affected if The build number falls below any of these thresholds: 10.0.10240.21073 (Win10 1507), 10.0.14393.8246 (Win10 1607), 10.0.17763.7558 (Win10 1809), 10.0.19044.6093 (Win10 21h2), 10.0.19045.6093 (Win10 22h2), 10.0.22621.5624 (Win11 22h2), 10.0.22631.5624 (Win11 23h2), or 10.0.26100.4652 (Win11 24h2)
  2. Verify NTFS is the active file system
    Open Command Prompt and run 'fsutil fsinfo volumeinfo C:' (or any local drive letter) to check if the filesystem is NTFS
    Affected if The filesystem is NTFS and the Windows build version is below the patched versions listed above (the vulnerability exists in the NTFS driver)
  3. Confirm current user context
    Open Command Prompt and run 'whoami /groups' to see the current user privilege level
    Affected if The user has authenticated access but is not already running as Administrator or SYSTEM, and the Windows build is vulnerable per the version checks above

You are affected if your Windows build number is lower than the threshold for your specific Windows version and you are running NTFS as your filesystem, since the vulnerability resides in the NTFS driver and can be exploited by authenticated local users to escalate to SYSTEM privileges.

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.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply Microsoft security updates for Windows NTFS as they become available through standard Windows Update or patch management deployment. Verify that endpoint protection and least-privilege configurations are in place to limit local attack surface.

Recommended fix High confidence

Upgrade to: Windows 10 1507 build >=10.0.10240.21073 | 1607 >=10.0.14393.8246 | 1809 >=10.0.17763.7558 | 21h2 >=10.0.19044.6093 | 22h2 >=10.0.19045.6093 | Windows 11 22h2 >=10.0.22621.5624 | 23h2 >=10.0.22631.5624 | 24h2 >=10.0.26100.4652

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify your Windows release (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2)
  3. Open Windows Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to download and install the latest security update
  5. Alternatively, manually install the update from Microsoft Update Catalog using KB number for your Windows version
  6. Restart the system after updates are installed
  7. Verify the installed version matches or exceeds the fixed build number for your release
Caveat Standard Windows cumulative update; may require restart and typical post-update verification

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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