Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-20925: CWE-73: External Control of File Name or Path in Microsoft Windows 10 Version 1809

0
Medium
VulnerabilityCVE-2026-20925cvecve-2026-20925cwe-73
Published: Tue Jan 13 2026 (01/13/2026, 17:56:41 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.

AI-Powered Analysis

AILast updated: 02/04/2026, 08:56:39 UTC

Technical Analysis

CVE-2026-20925 is a vulnerability classified under CWE-73 (External Control of File Name or Path) affecting Microsoft Windows 10 Version 1809 (build 10.0.17763.0). The issue arises from improper handling of file names or paths within the Windows NTLM authentication mechanism, which is widely used for network authentication in Windows environments. An attacker without any privileges can exploit this vulnerability remotely over the network, requiring user interaction, to perform spoofing attacks. Spoofing in this context means the attacker can manipulate the file path or name to deceive the system or users, potentially redirecting authentication attempts or causing disclosure of sensitive information. The vulnerability impacts confidentiality by allowing unauthorized access or information leakage but does not affect system integrity or availability. The CVSS v3.1 score is 6.5 (medium), reflecting the network attack vector, low attack complexity, no privileges required, but requiring user interaction. No known public exploits or patches are currently available, indicating that the vulnerability is newly disclosed and not yet actively exploited. The vulnerability is particularly relevant for environments still running Windows 10 Version 1809, which is an older release with extended support in some enterprise contexts. The lack of patches necessitates interim mitigations to reduce exposure. The vulnerability's exploitation could facilitate lateral movement or credential theft within enterprise networks, especially where NTLM authentication is prevalent and legacy protocols are enabled.

Potential Impact

For European organizations, this vulnerability poses a significant risk to confidentiality, especially in sectors relying on legacy Windows 10 Version 1809 systems and NTLM authentication. Attackers could leverage this flaw to spoof authentication requests, potentially gaining unauthorized access to sensitive data or network resources. This could lead to data breaches, exposure of intellectual property, or compromise of personal data protected under GDPR. The lack of impact on integrity and availability reduces the risk of system downtime or data manipulation but does not diminish the threat to information confidentiality. Organizations with extensive internal networks using NTLM for authentication are particularly vulnerable to lateral movement attacks facilitated by this flaw. The requirement for user interaction means phishing or social engineering could be vectors for exploitation, increasing risk in environments with less mature security awareness. The absence of known exploits currently provides a window for proactive defense, but the medium severity score indicates that exploitation could have meaningful consequences if leveraged by skilled attackers. The threat is heightened in critical infrastructure, government, and financial sectors where confidentiality breaches can have severe operational and reputational impacts.

Mitigation Recommendations

1. Disable or restrict NTLM authentication where possible, replacing it with more secure protocols like Kerberos. 2. Implement strict network segmentation to limit the spread of attacks leveraging NTLM spoofing. 3. Enforce least privilege access controls to minimize the impact of compromised credentials. 4. Educate users to recognize and avoid suspicious files or links that could trigger user interaction-based exploits. 5. Monitor network traffic for unusual NTLM authentication attempts or anomalies indicative of spoofing. 6. Apply all available Windows updates and security patches promptly once Microsoft releases a fix for this vulnerability. 7. Use endpoint detection and response (EDR) tools to detect and respond to suspicious activities related to NTLM authentication. 8. Consider deploying application whitelisting to prevent execution of unauthorized or malicious files that could exploit the vulnerability. 9. Review and harden Group Policy settings related to NTLM usage and authentication protocols. 10. Conduct regular vulnerability assessments and penetration testing focusing on authentication mechanisms and legacy systems.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2025-12-04T20:04:16.335Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69668ae3a60475309f9ae1cf

Added to database: 1/13/2026, 6:11:47 PM

Last enriched: 2/4/2026, 8:56:39 AM

Last updated: 2/7/2026, 9:00:26 PM

Views: 28

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats