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-20872: CWE-73: External Control of File Name or Path in Microsoft Windows 10 Version 1809

0
Medium
VulnerabilityCVE-2026-20872cvecve-2026-20872cwe-73
Published: Tue Jan 13 2026 (01/13/2026, 17:57:00 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: 01/27/2026, 19:23:17 UTC

Technical Analysis

CVE-2026-20872 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 flaw resides in the NTLM authentication mechanism, where an attacker can externally influence file names or paths used during the authentication process. This manipulation can lead to spoofing attacks over the network, allowing an unauthorized attacker to impersonate legitimate users or services. The vulnerability requires no privileges and no prior authentication, but does require user interaction, such as convincing a user to initiate a connection or authentication attempt. The CVSS v3.1 base score is 6.5, indicating a medium severity level, with high impact on confidentiality but no impact on integrity or availability. The attack vector is network-based, and the attack complexity is low, meaning exploitation is feasible in typical enterprise environments. No known exploits have been reported in the wild, and no official patches have been published yet, increasing the importance of interim mitigations. The vulnerability could be leveraged to bypass authentication controls, potentially exposing sensitive information or enabling further lateral movement within a network. Given the reliance of many organizations on Windows 10 and NTLM for legacy authentication, this vulnerability poses a tangible risk, especially in environments where NTLM cannot be fully disabled.

Potential Impact

For European organizations, the primary impact of CVE-2026-20872 lies in the potential compromise of confidentiality through spoofing attacks that could lead to unauthorized access to sensitive data or network resources. Organizations relying on Windows 10 Version 1809, particularly those with legacy systems or applications dependent on NTLM authentication, are at risk. The vulnerability could facilitate lateral movement by attackers within corporate networks, increasing the risk of data breaches or espionage. Critical sectors such as finance, government, healthcare, and energy, which often maintain legacy Windows environments, could face heightened exposure. The lack of patches and known exploits means organizations must act proactively to prevent exploitation. Additionally, the requirement for user interaction suggests phishing or social engineering could be used to trigger the attack, emphasizing the need for user awareness. Overall, the vulnerability could undermine trust in network authentication processes, potentially leading to regulatory and compliance challenges under GDPR and other European data protection laws.

Mitigation Recommendations

To mitigate CVE-2026-20872, European organizations should prioritize disabling NTLM authentication where feasible, replacing it with more secure protocols like Kerberos or certificate-based authentication. Network segmentation should be enforced to limit the exposure of vulnerable systems and reduce the attack surface. Implement strict access controls and monitor authentication logs for unusual or suspicious NTLM activity that could indicate exploitation attempts. Employ endpoint protection solutions capable of detecting anomalous network behavior related to NTLM spoofing. Conduct user training to reduce the risk of social engineering attacks that could trigger the vulnerability. Where disabling NTLM is not possible, apply group policies to restrict NTLM usage to trusted hosts only. Regularly update and patch systems once Microsoft releases an official fix. Additionally, consider deploying network-level protections such as SMB signing and enforcing SMB encryption to protect authentication traffic. Finally, integrate threat intelligence feeds to stay informed about emerging exploits targeting this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2025-12-03T05:54:20.382Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69668ae1a60475309f9ae169

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

Last enriched: 1/27/2026, 7:23:17 PM

Last updated: 2/2/2026, 6:27:01 PM

Views: 74

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