Windows 10 Version 1607: Improper Link Resolution Before File Access
CVE-2026-45586 is a high-severity improper link resolution before file access 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.9234 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 3.63% chance of exploitation within 30 days, higher than 90% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Windows 10 Version 1607 to 10.0.14393.9234 or a later version.
- Update Windows 10 Version 1809 to 10.0.17763.8880 or a later version.
- Update Windows 10 Version 21H2 to 10.0.19044.7417 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.9234 | 10.0.14393.9234 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.8880 | 10.0.17763.8880 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.7417 | 10.0.19044.7417 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.7417 | 10.0.19045.7417 |
| Microsoft | Windows 11 version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.7219 | 10.0.22631.7219 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.8655 | 10.0.26100.8655 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.8655 | 10.0.26200.8655 |
| Microsoft | Windows 11 version 26H1 | 10.0.28000.0 up to, but not including, 10.0.28000.2269 | 10.0.28000.2269 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.26132 | 6.2.9200.26132 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.26132 | 6.2.9200.26132 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.23228 | 6.3.9600.23228 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.23228 | 6.3.9600.23228 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.9234 | 10.0.14393.9234 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.9234 | 10.0.14393.9234 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.8880 | 10.0.17763.8880 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.8880 | 10.0.17763.8880 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.5256 | 10.0.20348.5256 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.32995 | 10.0.26100.32995 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.32995 | 10.0.26100.32995 |
| Microsoft | Windows 10 1607 | before 10.0.14393.9234 | 10.0.14393.9234 |
| Microsoft | Windows 10 1809 | before 10.0.17763.8880 | 10.0.17763.8880 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.7417 | 10.0.19044.7417 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.7417 | 10.0.19045.7417 |
| Microsoft | Windows 11 23h2 | before 10.0.22631.7219 | 10.0.22631.7219 |
| Microsoft | Windows 11 24h2 | before 10.0.26100.8655 | 10.0.26100.8655 |
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 link resolution before file access ('link following') in Windows Collaborative Translation Framework 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 Link Resolution Before File Access
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
How developers prevent this class of flaw
- Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.
More Improper Link Resolution Before File Access vulnerabilities (CWE-59)
Timeline
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Recent Improper Link Resolution Before File Access vulnerabilities
- 8.8 High severity
- 7.1 High severity
- 9.9 Critical severity
- 7.7 High severity
- 7.9 High severity
- 7.5 High severity
Spotted an error? Tell us.