dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-59506

HIGH · 7.0 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 →
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
Concurrent execution using shared resource with improper synchronization ('race condition') 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 race condition vulnerability in Windows DirectX allows an authenticated local attacker to exploit improper synchronization of shared resources during concurrent execution, potentially elevating their privileges to higher permission levels on the affected system.

MitigationApply the Microsoft security update for CVE-2025-59506 through Windows Update or enterprise patch management, then verify successful deployment across affected systems.

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 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. Identify Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build
    Affected if The build number falls below any of these thresholds: 14393.8594 (Win10 1607), 17763.8027 (Win10 1809), 19044.6575 (Win10 21h2), 19045.6575 (Win10 22h2), 22631.6199 (Win11 23h2), 26100.7092 (Win11 24h2), 26200.7092 (Win11 25h2), or if running Windows Server 2012/R2 (all versions)
  2. Confirm DirectX component presence
    Open Command Prompt and run 'dxdiag' to verify DirectX is loaded, or check for the presence of DirectX system files in C:\Windows\System32 such as dxgkrnl.sys
    Affected if DirectX is present on the system (it is installed by default on most Windows editions) and the Windows version meets the affected criteria from step 1
  3. Verify security update deployment status
    Open PowerShell and run 'Get-HotFix | Where-Object {$_.Description -like "*Security Update*"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recently installed security updates, or check Windows Update history for the CVE-2025-59506 update
    Affected if No security update addressing CVE-2025-59506 has been installed, meaning the system remains unpatched against this vulnerability

The system is affected if it runs any of the vulnerable Windows versions listed and lacks the corresponding security update for CVE-2025-59506.

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 CVE-2025-59506 through Windows Update or enterprise patch management, then verify successful deployment across affected systems.

Recommended fix High confidence

Upgrade to the specific fixed build version for your Windows release (e.g., Windows 10 22h2 to build 10.0.19045.6575 or later); for Windows Server 2012 R2, migrate to a supported Windows Server version (2016/2019/2022)

  1. Check the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify the specific Windows release (e.g., 10 1607, 10 1809, 10 21h2, 10 22h2, 11 23h2, 11 24h2, 11 25h2, or Server 2012 R2)
  3. For Windows 10/11: Navigate to Windows Update > Check for updates and install all available security updates, or manually download the specific KB from Microsoft Update Catalog for the build number matching the fixed version
  4. For Windows Server 2012 R2: Since the product is end-of-life with no patches available, migrate to a supported Windows Server version (2016 or later)
  5. After applying updates, verify the new build version matches or exceeds the fixed version numbers: 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
  6. Restart the system to ensure the DirectX components are fully updated
Caveat Windows Server 2012 R2 is end-of-life with no security updates; migration to a newer server version is required; test applications for compatibility before deploying OS updates in production

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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