Skip to main content
CVE-2025-32724VulnerabilityPublished Updated

CVE-2025-32724: Microsoft Windows 10 Version 1507 · Uncontrolled Resource Consumption

Affects Microsoft Windows 10 Version 1507Source 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
1.8% chance of exploitation in 30 days – higher than 78% 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 10 Jun 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 1507Affected
  • =10.0.10240.0
Fixed in–

AI-suggested

Since no official patches are currently available for CVE-2025-32724, organizations should implement the following specific mitigations: 1) Isolate or segment legacy Windows 10 Version 1507 systems from untrusted networks to reduce exposure. 2) Employ network-level filtering and intrusion prevention systems (IPS) to detect and block anomalous traffic targeting LSASS or exhibiting patterns consistent with resource exhaustion attacks. 3) Monitor system resource usage and LSASS process behavior closely to identify early signs of exploitation attempts. 4) Where feasible, upgrade affected systems to a supported, patched version of Windows 10 or later to eliminate the vulnerability. 5) Restrict network access to LSASS-related services using firewalls or access control lists (ACLs). 6) Implement rate limiting on network traffic to LSASS to prevent excessive request volumes. 7) Maintain comprehensive logging and alerting to facilitate rapid incident response. These targeted actions go beyond generic advice by focusing on containment, detection, and system hardening specific to the vulnerability's characteristics.

Description

Uncontrolled resource consumption in Windows Local Security Authority Subsystem Service (LSASS) allows an unauthorized attacker to deny service over a network.

References

Community reviews

Loading reviews…