dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-60716

HIGH · 7.0 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.17763.8027 / 10.0.19044.6575 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 DirectX 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 Windows DirectX allows a local authenticated attacker to elevate privileges. The flaw involves improper memory management where memory is accessed after being freed, potentially allowing an attacker to execute arbitrary code with elevated privileges.

MitigationApply Microsoft security updates for Windows when released; restrict local system access to essential personnel only; ensure least-privilege principles are followed.

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 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 2019Operating system
Affected:< 10.0.17763.8027
Windows Server 2022Operating system
Affected:< 10.0.20348.4346

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 10 build version
    Run 'winver' from command prompt or check System Properties to view the OS build number. Alternatively, run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The build number is less than 10.0.17763.8027 (Windows 10 1809), 10.0.19044.6575 (Windows 10 21h2), or 10.0.19045.6575 (Windows 10 22h2)
  2. Check Windows 11 build version
    Run 'winver' from command prompt or check System Properties to view the OS build number. Alternatively, run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The build number is less than 10.0.22631.6199 (Windows 11 23h2), 10.0.26100.7092 (Windows 11 24h2), or 10.0.26200.7092 (Windows 11 25h2)
  3. Check Windows Server version
    Run 'systeminfo' and check the OS Name and OS Version fields, or run 'winver'
    Affected if The build number is less than 10.0.17763.8027 (Windows Server 2019) or 10.0.20348.4346 (Windows Server 2022)
  4. Verify DirectX is present
    Run 'dxdiag' from command prompt and check that DirectX Diagnostic Tool loads successfully
    Affected if DirectX is installed and functional (the vulnerability exists in the DirectX subsystem, so its presence is required for the attack surface)

The system is affected if it runs any of the listed Windows versions with a build number below the specified threshold and has DirectX enabled.

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.17763.8027 / 10.0.19044.6575 / 10.0.19045.6575 or later
Fixed in 10.0.17763.802710.0.19044.657510.0.19045.6575
Interim mitigation

Apply Microsoft security updates for Windows when released; restrict local system access to essential personnel only; ensure least-privilege principles are followed.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.8027 or later | Windows 10 21h2: 10.0.19044.6575 or later | Windows 10 22h2: 10.0.19045.6575 or later | Windows 11 23h2: 10.0.22631.6199 or later | Windows 11 24h2: 10.0.26100.7092 or later | Windows 11 25h2: 10.0.26200.7092 or later | Windows Server 2019: 10.0.17763.8027

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine the appropriate security update for your Windows version from Microsoft Security Response Center (msrc.microsoft.com)
  3. Open Windows Update: Start > Settings > Update & Security > Windows Update
  4. Click 'Check for updates' and install all available security updates
  5. Alternatively, manually download and install the specific KB update for CVE-2025-60716 from the Microsoft Update Catalog
  6. Restart the system after installing the update
  7. Verify the update was installed by checking Windows Update history or running 'systeminfo' to confirm the build version matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply - ensure critical data is backed up before applying updates; some updates may require restart and could affect running services

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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