Skip to main content
CVE-2025-21351VulnerabilityPublished Updated

CVE-2025-21351: Microsoft Windows 10 Version 1607 · Uncontrolled Resource Consumption

Affects Microsoft Windows 10 Version 1607Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Feb 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Microsoft Windows 10 Version 1607Affected
  • =10.0.14393.0
Fixed in–

AI-suggested

1. Immediately restrict network access to Active Directory Domain Services APIs by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks. 2. Monitor system resource usage closely on Windows 10 Version 1607 systems, setting up alerts for unusual CPU or memory consumption patterns that may indicate exploitation attempts. 3. Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics tuned to detect anomalous Active Directory API traffic. 4. Prioritize upgrading or migrating systems from Windows 10 Version 1607 to supported, patched versions of Windows 10 or Windows 11 to eliminate the vulnerability. 5. Implement rate limiting or throttling on Active Directory API requests where possible to mitigate resource exhaustion. 6. Conduct regular audits of legacy systems and decommission unsupported operating systems to reduce attack surface. 7. Prepare incident response plans specifically addressing denial of service scenarios targeting directory services. 8. Engage with Microsoft support channels for any available workarounds or early patches and subscribe to security advisories for timely updates.

Description

Windows Active Directory Domain Services API Denial of Service Vulnerability

References

Community reviews

Loading reviews…