dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50371

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click 5 weeks old

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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows LUAFV allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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 race condition vulnerability exists in Windows LUAFV (Legacy Unicode ANSI File Virtualization) where concurrent execution improperly synchronizes shared resources, allowing an authorized attacker to elevate privileges locally to higher authority levels.

MitigationApply Microsoft security patches for LUAFV when available; implement least-privilege principles and restrict local admin access to reduce 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 1607Operating system
Affected:< 10.0.14393.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2525
Windows Server 2012Operating system
Affected:all versions= r2

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
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Version"' to obtain the exact build number, or check the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuild
    Affected if The build number is lower than the fixed version for your specific Windows release (e.g., below 10.0.14393.9339 for 1607, below 10.0.17763.9020 for 1809, below 10.0.19044.7548 for 21h2, below 10.0.19045.7548 for 22h2, below 10.0.26100.8875 for 11 24h2, below 10.0.26200.8875 for 11 25h2, or below 10.
  2. Confirm Windows 10 release
    Run 'winver' or check the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion to identify the specific release (1607, 1809, 21h2, or 22h2)
    Affected if You are on Windows 10 1607, 1809, 21h2, or 22h2 and the build is below the corresponding threshold
  3. Confirm Windows 11 or Server release
    Run 'winver' to identify if running Windows 11 24h2, 25h2, 26h1, or Windows Server 2012 R2
    Affected if You are on Windows 11 24h2, 25h2, 26h1 with build below threshold, or any Windows Server 2012 R2 version (all versions affected)
  4. Verify LUAFV service presence
    Open Services console (services.msc) or run 'sc query luafv' to check if the LUAFV service exists and its current status
    Affected if The LUAFV service is present on the system (this is the vulnerable component)
  5. Confirm LUAFV driver loaded
    Run 'sc queryex type= driver' or check Device Manager for 'luafv.sys' under non-plug and play drivers to verify the driver is loaded
    Affected if The luafv.sys driver is loaded and running on the system

Your system is affected if it runs a Windows version listed in the affected products AND the current build number is below the fixed threshold, with LUAFV service/driver present on the system.

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply Microsoft security patches for LUAFV when available; implement least-privilege principles and restrict local admin access to reduce attack surface.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9339 | Windows 10 1809: build 10.0.17763.9020 | Windows 10 21h2: build 10.0.19044.7548 | Windows 10 22h2: build 10.0.19045.7548 | Windows 11 24h2: build 10.0.26100.8875 | Windows 11 25h2: build 10.0.26200.8875 | Windows 11 26h1: build 10.0.28000.2525 | Windows Serve

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to install the latest cumulative security update for your Windows version
  3. Alternatively, manually install the specific KB patch for your Windows version from Microsoft Update Catalog
  4. Restart the system after applying the update
  5. Verify the installed build version matches or exceeds the fixed build number for your Windows release
Caveat Standard Windows update - minimal risk; ensure backups and test in non-production first

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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