Skip to main content
CVE-2025-49658VulnerabilityPublished Updated

CVE-2025-49658: Microsoft Windows 10 Version 1507 · Out-of-bounds Read

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.5% chance of exploitation in 30 days – higher than 45% 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 8 Jul 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 currently supported and patched version of Windows 10 or Windows 11 to eliminate exposure to this vulnerability. 2. Restrict local access to systems running legacy Windows 10 builds, enforcing strict access controls and monitoring for unauthorized local logins. 3. Implement robust endpoint detection and response (EDR) solutions to detect anomalous local activities that could indicate exploitation attempts. 4. Apply principle of least privilege to user accounts to minimize the risk posed by authorized local attackers. 5. Monitor Microsoft security advisories closely for the release of patches addressing CVE-2025-49658 and deploy them promptly once available. 6. For virtualization environments using TDX technology, consider additional isolation or encryption layers to protect sensitive data in memory. 7. Conduct security awareness training to inform internal users about the risks of local exploitation and insider threats. 8. Employ memory protection mechanisms and system integrity checks where feasible to detect abnormal memory access patterns. These steps go beyond generic advice by focusing on legacy system upgrades, local access restrictions, and virtualization-specific protections.

Description

Out-of-bounds read in Windows TDX.sys allows an authorized attacker to disclose information locally.

References

Community reviews

Loading reviews…