dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-50158

HIGH · 7.0 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.10240.21100 / 10.0.14393.8330 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Time-of-check time-of-use (toctou) race condition in Windows NTFS allows an unauthorized 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

A time-of-check time-of-use (TOCTOU) race condition in Windows NTFS allows a local unauthorized attacker to exploit the timing window between checking file metadata and accessing the file, potentially disclosing sensitive information they should not have access to.

MitigationApply Microsoft security updates for this NTFS vulnerability; ensure least-privilege file permissions and monitor for suspicious local access patterns in the interim.

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.21100
Windows 10 1607Operating system
Affected:< 10.0.14393.8330
Windows 10 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851

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

CVSS:3.1/AV:L/AC:H/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. Check Windows build number
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Version"' to display the installed Windows build version
    Affected if The build number falls below any of these thresholds: 10.0.10240.21100 (Win10 1507), 10.0.14393.8330 (Win10 1607), 10.0.17763.7678 (Win10 1809), 10.0.19044.6216 (Win10 21h2), 10.0.19045.6216 (Win10 22h2), 10.0.22621.5768 (Win11 22h2), 10.0.22631.5768 (Win11 23h2), 10.0.26100.4851 (Win11 24h2)
  2. Verify NTFS filesystem is in use
    Run 'fsutil fsinfo volumeinfo C:' (replace C: with any target drive letter) and examine the output for "File System Name : NTFS"
    Affected if The filesystem is NTFS and the Windows build number is below the affected thresholds listed above
  3. Check CurrentVersion registry key
    Read the registry value at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion, specifically the 'CurrentBuild' and 'DisplayVersion' fields to determine exact version
    Affected if The build number extracted from the registry is lower than the affected thresholds for your Windows release

You are affected if your Windows installation uses NTFS and the installed build number is lower than the threshold specified for your Windows version (10/11 release and build).

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.21100 / 10.0.14393.8330 / 10.0.17763.7678 or later
Fixed in 10.0.10240.2110010.0.14393.833010.0.17763.7678
Interim mitigation

Apply Microsoft security updates for this NTFS vulnerability; ensure least-privilege file permissions and monitor for suspicious local access patterns in the interim.

Recommended fix High confidence

Upgrade to the minimum fixed version for your Windows release: Windows 10 1507 to 10.0.10240.21100, Windows 10 1607 to 10.0.14393.8330, Windows 10 1809 to 10.0.17763.7678, Windows 10 21h2 to 10.0.19044.6216, Windows 10 22h2 to 10.0.19045.6216, Windows 11 22h2 to 10.0.22621.5768, Windows 11 23h2 to 1

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows release channel the system is on (e.g., Windows 10 22h2, Windows 11 23h2)
  3. For Windows 10 systems: Apply the cumulative update for the specific version - Windows 10 version 1507 requires 10.0.10240.21100 or later, version 1607 requires 10.0.14393.8330 or later, version 1809 requires 10.0.17763.7678 or later, version 21h2 requires 10.0.19044.6216 or later, version 22h2 requires 10.0.19045.6216 or later
  4. For Windows 11 systems: Version 22h2 requires 10.0.22621.5768 or later, version 23h2 requires 10.0.22631.5768 or later, version 24h2 requires 10.0.26100.4851 or later
  5. Use Windows Update (Settings > Update & Security > Windows Update) or download the appropriate cumulative update from the Microsoft Update Catalog
  6. Restart the system after applying the update
Caveat Standard Windows cumulative update - may require restart; verify application compatibility in enterprise environments

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
  • 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-2025-50158 — 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-50158 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