dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-27908

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
Use after free in Windows TDI Translation Driver (tdx.sys) 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 use-after-free vulnerability in the Windows TDI Translation Driver (tdx.sys) allows a locally authenticated attacker to manipulate memory after it has been freed, potentially achieving elevated privileges on the affected system.

MitigationApply available Microsoft security updates for Windows that address the tdx.sys vulnerability. Prioritize patching systems with direct user access, as the attack requires local authentication.

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
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build number
    Affected if The build number falls below any of these thresholds: 14393.9060 (Win10 1607), 17763.8644 (Win10 1809), 19044.7184 (Win10 21h2/22h2), 22631.6936 (Win11 23h2), 26100.8246 (Win11 24h2/25h2), or 28000.1836 (Win11 26h1)
  2. Verify tdx.sys driver presence
    Check if the driver file exists at the system driver location using 'dir C:\Windows\System32\drivers\tdx.sys' in an elevated Command Prompt
    Affected if The tdx.sys file exists on the system, as the vulnerability resides in this driver
  3. Check driver version information
    Right-click tdx.sys in File Explorer, select Properties, then view the Details tab for version information, or use 'powershell (Get-Item C:\Windows\System32\drivers\tdx.sys).VersionInfo'
    Affected if Driver version information is displayed, confirming the driver is installed
  4. Confirm local authentication requirement
    Verify that the system allows local user access (interactive logon, RDP, or physical access), as the attacker needs local authentication to exploit this vulnerability
    Affected if Local user accounts or interactive sessions are enabled on the system

A system is affected if it runs a Windows version with a build number lower than the patched thresholds AND has tdx.sys present, with the attacker requiring local authentication to attempt exploitation.

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 available Microsoft security updates for Windows that address the tdx.sys vulnerability. Prioritize patching systems with direct user access, as the attack requires local authentication.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9060 or later | Windows 10 1809: build 10.0.17763.8644 or later | Windows 10 21h2: build 10.0.19044.7184 or later | Windows 10 22h2: build 10.0.19045.7184 or later | Windows 11 23h2: build 10.0.22631.6936 or later | Windows 11 24h2: build 10.0.26100.8246 or later |

  1. 1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows version and build category applies to your system from the affected versions list
  3. 3. Apply Windows Updates: Open Settings > Update & Security > Windows Update and check for updates
  4. 4. Install the cumulative security update that includes the fix for CVE-2026-27908
  5. 5. Restart the system when prompted to complete the update installation
  6. 6. Verify the installed build version meets or exceeds the minimum fixed version for your Windows release
Caveat Standard Windows cumulative update risks - ensure backup of critical data before applying updates; some updates may require compatibility re-testing of custom applications

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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