Skip to main content
CVE-2025-59211VulnerabilityPublished Updated

CVE-2025-59211: Microsoft Windows 10 Version 1507 · Information Exposure

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, 06:26 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Microsoft Windows 10 Version 1507Affected
  • =10.0.10240.0
Fixed in–

AI-suggested

1. Upgrade affected systems from Windows 10 Version 1507 to a supported, fully patched version of Windows 10 or later to eliminate the vulnerability. 2. Restrict local access to systems running legacy Windows versions by enforcing strict physical security and limiting user accounts with local login privileges. 3. Implement robust endpoint detection and response (EDR) solutions to monitor for suspicious local activity that could indicate attempts to exploit this vulnerability. 4. Apply the principle of least privilege to user accounts, ensuring that users have only the minimum necessary permissions to reduce the risk of exploitation. 5. Use application whitelisting and control execution policies to prevent unauthorized code execution that could leverage leaked information. 6. Regularly audit and review local user accounts and access logs to detect unauthorized access attempts. 7. Stay informed on Microsoft security advisories for any forthcoming patches or mitigations related to this vulnerability. 8. Consider network segmentation to isolate legacy systems and limit the potential impact of local compromise.

Description

Exposure of sensitive information to an unauthorized actor in Windows Push Notification Core allows an authorized attacker to disclose information locally.

References

Community reviews

Loading reviews…