CVE-2026-21249: CWE-73: External Control of File Name or Path in Microsoft Windows 10 Version 1607
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing locally.
AI Analysis
Technical Summary
CVE-2026-21249 is a vulnerability classified under CWE-73 (External Control of File Name or Path) affecting Microsoft Windows 10 Version 1607 (build 10.0.14393.0). The issue arises from the NTLM authentication process where an attacker with local access can manipulate file names or paths used by the system, enabling spoofing attacks. Spoofing here implies that the attacker can deceive the system or users by presenting falsified file paths or names, potentially leading to misdirected operations or data exposure. The vulnerability requires local access and user interaction, meaning an attacker must be able to execute code or actions on the affected machine and trick a user into triggering the exploit. The CVSS v3.1 score is 3.3, indicating low severity, primarily because the attack vector is local, no privileges are required, but user interaction is necessary, and the impact on confidentiality is limited with no effect on integrity or availability. No known exploits have been reported in the wild, and no official patches have been released at the time of publication. This vulnerability is relevant mainly to legacy systems still running Windows 10 Version 1607, which reached end of mainstream support years ago, but may still be in use in some environments. The flaw highlights the risks of outdated OS versions and the importance of maintaining up-to-date systems. Attackers exploiting this vulnerability could potentially spoof file paths to mislead users or software components, possibly facilitating further local attacks or evasion of security controls.
Potential Impact
For European organizations, the impact of CVE-2026-21249 is generally low due to the limited scope and conditions required for exploitation. However, organizations still operating legacy Windows 10 Version 1607 systems, particularly in critical infrastructure sectors such as manufacturing, healthcare, or government, could face localized risks. Spoofing attacks leveraging this vulnerability might enable attackers to mislead users or software processes, potentially leading to unauthorized access to local resources or bypassing security mechanisms. While the vulnerability does not directly compromise system integrity or availability, it could be used as a stepping stone for more complex local attacks if combined with other vulnerabilities. The requirement for local access and user interaction limits remote exploitation, reducing the threat surface. Nonetheless, in environments with shared workstations or insufficient endpoint security, the risk is elevated. European organizations with strict compliance requirements should consider this vulnerability in their risk assessments, especially if legacy systems are still in operation.
Mitigation Recommendations
To mitigate CVE-2026-21249 effectively, European organizations should prioritize upgrading affected systems from Windows 10 Version 1607 to a supported and patched Windows version to eliminate the vulnerability entirely. In the interim, restrict local user privileges to the minimum necessary to reduce the risk of local exploitation. Implement strict application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious local activities that could exploit file path manipulation. Educate users about the risks of interacting with untrusted local files or prompts that could trigger spoofing attacks. Regularly audit and harden NTLM authentication configurations, considering disabling NTLM where feasible in favor of more secure protocols like Kerberos. Employ network segmentation to limit the impact of compromised local accounts. Since no patches are currently available, maintaining robust local security controls and planning timely OS upgrades are critical. Additionally, monitor security advisories from Microsoft for any forthcoming patches or mitigations related to this vulnerability.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Poland, Netherlands
CVE-2026-21249: CWE-73: External Control of File Name or Path in Microsoft Windows 10 Version 1607
Description
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing locally.
AI-Powered Analysis
Technical Analysis
CVE-2026-21249 is a vulnerability classified under CWE-73 (External Control of File Name or Path) affecting Microsoft Windows 10 Version 1607 (build 10.0.14393.0). The issue arises from the NTLM authentication process where an attacker with local access can manipulate file names or paths used by the system, enabling spoofing attacks. Spoofing here implies that the attacker can deceive the system or users by presenting falsified file paths or names, potentially leading to misdirected operations or data exposure. The vulnerability requires local access and user interaction, meaning an attacker must be able to execute code or actions on the affected machine and trick a user into triggering the exploit. The CVSS v3.1 score is 3.3, indicating low severity, primarily because the attack vector is local, no privileges are required, but user interaction is necessary, and the impact on confidentiality is limited with no effect on integrity or availability. No known exploits have been reported in the wild, and no official patches have been released at the time of publication. This vulnerability is relevant mainly to legacy systems still running Windows 10 Version 1607, which reached end of mainstream support years ago, but may still be in use in some environments. The flaw highlights the risks of outdated OS versions and the importance of maintaining up-to-date systems. Attackers exploiting this vulnerability could potentially spoof file paths to mislead users or software components, possibly facilitating further local attacks or evasion of security controls.
Potential Impact
For European organizations, the impact of CVE-2026-21249 is generally low due to the limited scope and conditions required for exploitation. However, organizations still operating legacy Windows 10 Version 1607 systems, particularly in critical infrastructure sectors such as manufacturing, healthcare, or government, could face localized risks. Spoofing attacks leveraging this vulnerability might enable attackers to mislead users or software processes, potentially leading to unauthorized access to local resources or bypassing security mechanisms. While the vulnerability does not directly compromise system integrity or availability, it could be used as a stepping stone for more complex local attacks if combined with other vulnerabilities. The requirement for local access and user interaction limits remote exploitation, reducing the threat surface. Nonetheless, in environments with shared workstations or insufficient endpoint security, the risk is elevated. European organizations with strict compliance requirements should consider this vulnerability in their risk assessments, especially if legacy systems are still in operation.
Mitigation Recommendations
To mitigate CVE-2026-21249 effectively, European organizations should prioritize upgrading affected systems from Windows 10 Version 1607 to a supported and patched Windows version to eliminate the vulnerability entirely. In the interim, restrict local user privileges to the minimum necessary to reduce the risk of local exploitation. Implement strict application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious local activities that could exploit file path manipulation. Educate users about the risks of interacting with untrusted local files or prompts that could trigger spoofing attacks. Regularly audit and harden NTLM authentication configurations, considering disabling NTLM where feasible in favor of more secure protocols like Kerberos. Employ network segmentation to limit the impact of compromised local accounts. Since no patches are currently available, maintaining robust local security controls and planning timely OS upgrades are critical. Additionally, monitor security advisories from Microsoft for any forthcoming patches or mitigations related to this vulnerability.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- microsoft
- Date Reserved
- 2025-12-11T21:02:05.736Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 698b76004b57a58fa120a029
Added to database: 2/10/2026, 6:16:32 PM
Last enriched: 2/18/2026, 8:35:15 AM
Last updated: 2/21/2026, 12:22:03 AM
Views: 39
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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.