CVE-2025-50154VulnerabilityPublished 12 Aug 2025Updated 13 Feb 2026

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

Affects Microsoft Windows 10 Version 1507Source CVE Database V5

Not known to be exploited · public exploit available (Exploit-DB) · 29% EPSS · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 29.7% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Exploit-DB entry, 6 days after disclosure
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by microsoft
2025-06-1318:35Z, 60 days before disclosure
CVE published
on cve.org
2025-08-1217:09Z, t = 0
In Threat Radar
record ingested
2025-08-1217:18Z, 8 minutes after disclosure
First Exploit-DB entry (opens in a new tab)
Microsoft Windows 10.0.19045 - NTLMv2 Hash Disclosure
2025-08-18, 6 days after disclosure

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Microsoft Windows 10 Version 1507	Affected =10.0.10240.0	Fixed in–

AI-suggested

1. Upgrade all Windows 10 systems to the latest supported version to eliminate exposure to this vulnerability, as Windows 10 Version 1507 is outdated and unsupported. 2. Until upgrades are complete, restrict network access to Windows File Explorer shares and disable SMBv1 and other legacy protocols that may facilitate exploitation. 3. Implement strict network segmentation to limit exposure of vulnerable systems to untrusted networks. 4. Educate users about the risks of interacting with unsolicited network resources and enforce policies to reduce risky user interactions. 5. Monitor network traffic for unusual spoofing or reconnaissance activity that could indicate exploitation attempts. 6. Employ endpoint detection and response (EDR) tools to identify suspicious behavior related to network spoofing or information disclosure. 7. Apply group policy settings to disable or restrict Windows File Explorer network features where feasible. 8. Maintain up-to-date backups and incident response plans to quickly recover if exploitation occurs. 9. Engage with Microsoft support channels for any forthcoming patches or advisories related to this CVE. 10. Conduct regular vulnerability assessments focusing on legacy systems to identify and remediate similar risks.

Description

Exposure of sensitive information to an unauthorized actor in Windows File Explorer allows an unauthorized attacker to perform spoofing over a network.

Impact

For European organizations, the primary impact of CVE-2025-50154 is the unauthorized disclosure of sensitive information, which could lead to privacy breaches, intellectual property theft, or exposure of internal network details. This information exposure can facilitate more sophisticated attacks such as credential theft, phishing, or network spoofing. Organizations in sectors with stringent data protection regulations like GDPR could face compliance risks and reputational damage if sensitive data is leaked. The vulnerability does not directly affect system integrity or availability, so operational disruption is unlikely. However, the requirement for user interaction means that social engineering or phishing campaigns could increase the risk of exploitation. Legacy systems still running Windows 10 Version 1507, particularly in critical infrastructure, manufacturing, or government sectors, may be vulnerable if not upgraded. The lack of patches means organizations must rely on compensating controls, increasing operational complexity. Overall, the impact is moderate but significant enough to warrant immediate attention in environments with legacy Windows 10 deployments.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Feb 2026, 10:38 UTC

Public exploits and detection1 Exploit-DB entry

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats