dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-50172

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.17763.7678 / 10.0.19044.6216 or later.
See remediation →
71/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
Allocation of resources without limits or throttling 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

Windows DirectX contains a vulnerability where resource allocation occurs without proper limits or throttling, allowing an authenticated attacker to cause a denial of service by exhausting system resources through network-based requests.

MitigationApply Microsoft security updates for Windows DirectX when released; implement network-level rate limiting and monitoring as an interim control to detect resource exhaustion attempts.

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.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851
Windows Server 2019Operating system
Affected:< 10.0.17763.7678
Windows Server 2022Operating system
Affected:< 10.0.20348.3989

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build number
    Affected if The version and build number fall below any of the following thresholds: Windows 10 1809/Server 2019 < 10.0.17763.7678, Windows 10 21h2 < 10.0.19044.6216, Windows 10 22h2 < 10.0.19045.6216, Windows 11 22h2 < 10.0.22621.5768, Windows 11 23h2 < 10.0.22631.5768, Windows 11 24h2 < 10.0.26100.4851, Windo
  2. Verify DirectX component presence
    Run 'dxdiag' or check for the presence of DirectX system files in %WINDIR%\System32 (such as d3d9.dll, d3d10.dll, d3d11.dll, dxgi.dll)
    Affected if DirectX components are installed and the Windows version is in the affected range listed above
  3. Monitor for abnormal resource consumption
    Use Task Manager or Performance Monitor to track CPU, memory, and handle usage over time. Run 'typeperf "\Process(dx*)\# Instances"' to monitor DirectX-related processes
    Affected if Unusually high resource usage by DirectX-related processes is observed without an explicit user workload explanation

You are affected if your Windows version is below the specified build numbers AND DirectX is installed, as the vulnerability allows authenticated attackers to exhaust system resources through DirectX network requests.

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.7678 / 10.0.19044.6216 / 10.0.19045.6216 or later
Fixed in 10.0.17763.767810.0.19044.621610.0.19045.6216
Interim mitigation

Apply Microsoft security updates for Windows DirectX when released; implement network-level rate limiting and monitoring as an interim control to detect resource exhaustion attempts.

Recommended fix High confidence

Windows 10 1809/Server 2019: build 10.0.17763.7678 or later | Windows 10 21h2: build 10.0.19044.6216 or later | Windows 10 22h2: build 10.0.19045.6216 or later | Windows 11 22h2: build 10.0.22621.5768 or later | Windows 11 23h2: build 10.0.22631.5768 or later | Windows 11 24h2: build 10.0.26100.4851

  1. Open Settings on the Windows system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative update
  4. Alternatively, manually install the appropriate security update from the Microsoft Update Catalog for your specific Windows version
  5. Restart the system after the update is installed
  6. Verify the build number matches or exceeds the fixed version (e.g., 10.0.17763.7678 for Windows 10 1809/Server 2019)

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
  • 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-2025-50172 — 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-50172 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