dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-60720

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 or later.
See remediation →
80/100
Remediation priority · High
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
Buffer over-read in Windows 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

Buffer over-read vulnerability in Windows TDX.sys kernel driver enables a locally authorized attacker to read beyond allocated buffer boundaries, potentially exposing sensitive kernel memory and achieving privilege escalation to SYSTEM level.

MitigationApply the Microsoft security update for TDX.sys once released; prioritize patching on systems where local unprivileged users have access, as exploitation requires local access but not administrator privileges.

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.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2008Operating 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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 if TDX.sys driver exists
    Open File Explorer and navigate to C:\Windows\System32\drivers\tdx.sys, or run: dir C:\Windows\System32\drivers\tdx.sys
    Affected if File does not exist - the vulnerability does not apply because the TDX driver is not installed on this system
  2. Get TDX.sys file version
    Right-click tdx.sys in File Explorer, select Properties, go to Details tab and note the File version field; or run: wmic datafile where "name='C:\\Windows\\System32\\drivers\\tdx.sys'" get Version
    Affected if The version shown is lower than the version in the affected ranges for your Windows build (10.0.14393.8594, 10.0.17763.8027, 10.0.19044.6575, 10.0.19045.6575, 10.0.22631.6199, 10.0.26100.7092, or 10.0.26200.7092 depending on your Windows version)
  3. Verify Windows version and build
    Run winver or go to Settings > System > About to find your Windows version and build number
    Affected if Your Windows build number is lower than the fix version for your specific Windows release (see the affected version list for your Windows 10/11 or Server version)
  4. Check if TDX driver service is present
    Run: sc query tdx or Get-Service -Name TDX in PowerShell
    Affected if Service state shows as running or stopped - the vulnerable driver component is present on this system

You are affected if TDX.sys is present on your system AND your Windows version/build is lower than the corresponding fix version for your Windows release.

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.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply the Microsoft security update for TDX.sys once released; prioritize patching on systems where local unprivileged users have access, as exploitation requires local access but not administrator privileges.

Recommended fix High confidence

Install the latest Windows security updates for your Windows version; fixed builds are: Windows 10 1607: 10.0.14393.8594+, Windows 10 1809: 10.0.17763.8027+, Windows 10 21h2: 10.0.19044.6575+, Windows 10 22h2: 10.0.19045.6575+, Windows 11 23h2: 10.0.22631.6199+, Windows 11 24h2: 10.0.26100.7092+, Wi

  1. Identify the current Windows build 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 security updates from Microsoft
  4. Alternatively, manually download the specific KB update for this CVE from the Microsoft Update Catalog (search by CVE number)
  5. Restart the system after updates are installed
  6. Verify the build number matches or exceeds the fixed version for your Windows release (e.g., for Windows 10 22h2, verify build is 10.0.19045.6575 or higher)
Caveat Standard Windows update process; no breaking changes expected for patch installation. Windows Server 2008/R2 has no patch available and requires system replacement.

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
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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