Skip to main content
CVE-2025-59200VulnerabilityPublished Updated

CVE-2025-59200: Microsoft Windows 10 Version 1507 · Race Condition

Affects Microsoft Windows 10 Version 1507Source CVE Database V5

0

Not known to be exploited · CVSS 7.7 High.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 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 1507Affected
  • =10.0.10240.0
Fixed in–

AI-suggested

1. Apply official patches or updates from Microsoft as soon as they become available for Windows 10 Version 1507 to address this race condition vulnerability. 2. Restrict local user access on affected systems by enforcing strict user account control policies and limiting the ability to execute untrusted code. 3. Employ application whitelisting to prevent unauthorized or malicious programs from running locally. 4. Monitor local system logs and behavior for signs of suspicious activity indicative of race condition exploitation or spoofing attempts. 5. Consider upgrading affected systems to a supported and fully patched version of Windows 10 or later to eliminate exposure to legacy vulnerabilities. 6. Implement endpoint detection and response (EDR) solutions capable of detecting anomalous local process behavior related to race conditions or spoofing. 7. Educate users about the risks of running untrusted applications and the importance of reporting unusual system behavior. 8. In environments where legacy systems must remain, isolate them from sensitive networks and data to reduce potential impact.

Description

Concurrent execution using shared resource with improper synchronization ('race condition') in Data Sharing Service Client allows an unauthorized attacker to perform spoofing locally.

References

Community reviews

Loading reviews…