Skip to main content
VulnerabilityPublished Updated

CVE-2025-59203: Microsoft Windows 10 Version 1507 · Sensitive Data in Logs

Affects Microsoft Windows 10 Version 1507Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/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

First, restrict local access to affected Windows 10 Version 1507 systems to trusted personnel only, minimizing the attack surface. Employ strict access control and auditing on log files to prevent unauthorized reading or copying. Consider disabling or limiting the use of the StateRepository API if feasible, or isolate affected systems from sensitive environments. Use endpoint detection and response (EDR) tools to monitor for suspicious local access or log file access patterns. Where possible, upgrade or migrate systems from the legacy Windows 10 Version 1507 to supported versions with security updates. Implement data encryption for logs or use secure logging frameworks that redact sensitive information. Conduct regular security reviews and user privilege audits to ensure minimal necessary access. Finally, maintain awareness of vendor updates for patches or advisories addressing this vulnerability.

Description

Insertion of sensitive information into log file in Windows StateRepository API allows an authorized attacker to disclose information locally.

References

Community reviews

Loading reviews…