Windows 10 Version 1607: Improper Limitation of a Pathname to a Restricted Directory
CVE-2026-69445 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.14393.9512 as the first without the flaw, so updating Windows 10 Version 1607 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.37% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Windows 10 Version 1607 to 10.0.14393.9512 or a later version.
- Update Windows 10 Version 1809 to 10.0.17763.9245 or a later version.
- Update Windows 10 Version 21H2 to 10.0.19044.7725 or a later version.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.9512 | 10.0.14393.9512 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.9245 | 10.0.17763.9245 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.7725 | 10.0.19044.7725 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.7725 | 10.0.19045.7725 |
| Microsoft | Windows 11 version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.7582 | 10.0.22631.7582 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.9445 | 10.0.26100.9445 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.9445 | 10.0.26200.9445 |
| Microsoft | Windows 11 version 26H1 | 10.0.28000.0 up to, but not including, 10.0.28000.2954 | 10.0.28000.2954 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.26349 | 6.2.9200.26349 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.26349 | 6.2.9200.26349 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.23398 | 6.3.9600.23398 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.23398 | 6.3.9600.23398 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.9512 | 10.0.14393.9512 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.9512 | 10.0.14393.9512 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.9245 | 10.0.17763.9245 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.9245 | 10.0.17763.9245 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.5622 | 10.0.20348.5622 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.33438 | 10.0.26100.33438 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.33438 | 10.0.26100.33438 |
| Microsoft | Windows 10 1607 | before 10.0.14393.9512 | 10.0.14393.9512 |
| Microsoft | Windows 10 1809 | before 10.0.17763.9245 | 10.0.17763.9245 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.7725 | 10.0.19044.7725 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.7725 | 10.0.19045.7725 |
| Microsoft | Windows 11 23h2 | before 10.0.22631.7582 | 10.0.22631.7582 |
| Microsoft | Windows 11 24h2 | before 10.0.26100.9445 | 10.0.26100.9445 |
Version data comes from the organisation that assigned the CVE; 2 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Improper limitation of a pathname to a restricted directory ('path traversal') in Windows Compressed Folder allows an authorized attacker to elevate privileges locally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 9.0 Critical severity
- 7.6 High severity
- 7.4 High severity
- 7.2 High severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.