dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-60723

MEDIUM · 6.3 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 →
69/100
Remediation priority · Elevated
Remotely reachable 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 deny service over a network.

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 exists in Windows DirectX where concurrent execution shares resources without proper synchronization. An authorized attacker can exploit this improper synchronization to trigger a denial of service condition over a network.

MitigationApply Microsoft security updates for Windows DirectX when released; enforce strict network access controls to limit exposure to authorized users only.

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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/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
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to view the build number. For PowerShell, use '[System.Environment]::OSVersion.Version'
    Affected if The build version is below 17763.8027 (Windows 10 1809), 19044.6575 (Windows 10 21h2), or 19045.6575 (Windows 10 22h2)
  2. Check Windows 11 build version
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to view the build number. For PowerShell, use '[System.Environment]::OSVersion.Version'
    Affected if The build version is below 22631.6199 (Windows 11 23h2), 26100.7092 (Windows 11 24h2), or 26200.7092 (Windows 11 25h2)
  3. Check Windows Server build version
    Open Command Prompt and run 'systeminfo | findstr /B /C:"OS Version"' or use 'winver' if Desktop Experience is installed. For PowerShell, use 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber'
    Affected if The build version is below 17763.8027 (Windows Server 2019) or 20348.4346 (Windows Server 2022)
  4. Verify DirectX component presence
    Run 'dxdiag' from Command Prompt to launch DirectX Diagnostic Tool. Check if DirectX version is displayed and the tool loads successfully
    Affected if DirectX diagnostic tool runs successfully, indicating DirectX is installed and could be targeted by this vulnerability

You are affected if your Windows build version falls below the threshold for your specific Windows edition and DirectX is installed 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.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 DirectX when released; enforce strict network access controls to limit exposure to authorized users only.

Recommended fix High confidence

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 | Windows 11 25h2: 10.0.26200.7092 | Windows Server 2019: 10.0.17763.8027 | Windows Server 2022: 10.0.20348.4346

  1. Identify the installed Windows version and build number (winver or systeminfo)
  2. Determine which affected version range applies to your system
  3. Apply the relevant Windows security update for CVE-2025-60723 from Windows Update or Microsoft Update Catalog
  4. Reboot the system as prompted to complete the update
  5. Verify the installed build matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update; may require reboot

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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