dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-27929

HIGH · 7.0 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 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
Time-of-check time-of-use (toctou) race condition in Windows LUAFV 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

A time-of-check time-of-use (TOCTOU) race condition in Windows LUAFV (Lua Virtual Machine Filter Driver) allows a local authorized attacker to elevate privileges by exploiting the gap between security state checks and the actual use of that state in file operations.

MitigationApply the relevant Microsoft security update for LUAFV when released; until then, minimize local user privileges and monitor for suspicious driver interactions.

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.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

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. Identify Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from Command Prompt
    Affected if The build number is lower than the threshold for your Windows release (10.0.14393.9060 for 1607, 10.0.17763.8644 for 1809, 10.0.19044.7184 for 21h2, 10.0.19045.7184 for 22h2, 10.0.22631.6936 for 23h2, 10.0.26100.8246 for 24h2, 10.0.26200.8246 for 25h2, 10.0.28000.1836 for 26h1)
  2. Confirm LUAFV driver is loaded
    Run 'sc query luafv' from Command Prompt to check if the LUAFV service/driver is present and running
    Affected if The service state shows as RUNNING and the product version is unpatched per step 1
  3. Check for LUAFV driver file version
    Locate luafv.sys in System32\drivers and run 'driverquery /v | findstr luafv' or right-click the file to view Properties > Details
    Affected if The driver file version is older than the security update version for your Windows build
  4. Review security event logs for LUAFV anomalies
    Open Event Viewer and navigate to Application and Security logs, filter for events involving LUAFV or file virtualization warnings
    Affected if Unexpected or suspicious LUAFV file operation events appear, especially from low-privilege processes accessing protected locations

Your environment is affected if you run any of the listed Windows versions with a build number lower than the corresponding threshold AND the LUAFV driver is active 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.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply the relevant Microsoft security update for LUAFV when released; until then, minimize local user privileges and monitor for suspicious driver interactions.

Recommended fix High confidence

Install the Windows Security Update containing the fix for CVE-2026-27929. For each affected Windows version, the fixed builds are: Windows 10 1607 -> 10.0.14393.9060, Windows 10 1809 -> 10.0.17763.8644, Windows 10 21h2 -> 10.0.19044.7184, Windows 10 22h2 -> 10.0.19045.7184, Windows 11 23h2 -> 10.0.

  1. Identify the current Windows version by running `winver` or `systeminfo` from command prompt
  2. Open Windows Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative security update
  4. Alternatively, manually install the relevant security patch from Microsoft Update Catalog corresponding to your Windows version (search for the KB number released for this CVE)
  5. Restart the system when prompted to complete the installation
  6. Verify the update was applied by checking the installed updates or confirming the OS build number matches or exceeds the fixed version for your release
Caveat Standard Windows security update; no expected breaking changes for typical users. As this is a local privilege escalation fix, no configuration changes are 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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
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,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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