Skip to main content
VulnerabilityPublished Updated

CVE-2025-50172: Microsoft Windows 10 Version 1809 · Unthrottled Resource Allocation

Affects Microsoft Windows 10 Version 1809Source CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Microsoft Windows 10 Version 1809Affected
  • =10.0.17763.0
Fixed in–

AI-suggested

To mitigate CVE-2025-50172, European organizations should implement several targeted measures beyond generic advice: 1) Prioritize upgrading or migrating systems from Windows 10 Version 1809 to supported, patched Windows versions to eliminate the vulnerability. 2) Restrict network access to systems running the vulnerable version by implementing strict firewall rules, network segmentation, and access controls to limit exposure. 3) Monitor resource usage metrics closely on systems with DirectX to detect abnormal spikes indicative of exploitation attempts. 4) Employ endpoint detection and response (EDR) tools to identify suspicious activities related to resource exhaustion or unusual DirectX usage patterns. 5) Enforce least privilege principles to reduce the number of users with authorized access capable of exploiting the vulnerability. 6) Prepare incident response plans specifically addressing denial of service scenarios caused by resource exhaustion. 7) Stay informed on vendor advisories for patches or workarounds and apply them promptly once available. 8) Consider disabling or limiting DirectX features on systems where it is not essential to reduce the attack surface. These steps collectively reduce the risk and impact of exploitation while maintaining operational continuity.

Description

Allocation of resources without limits or throttling in Windows DirectX allows an authorized attacker to deny service over a network.

References

Community reviews

Loading reviews…