Windows 10 Version 1507: External Control of File Name or Path
CVE-2025-59200 is a high-severity external control of file name or path vulnerability in Windows 10 Version 1507 from Microsoft, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 10.0.10240.21161 as the first without the flaw, so updating Windows 10 Version 1507 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.8% chance of exploitation within 30 days, higher than 57% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Windows 10 Version 1507 to 10.0.10240.21161 or a later version.
- Update Windows 10 Version 1607 to 10.0.14393.8519 or a later version.
- Update Windows 10 Version 1809 to 10.0.17763.7919 or a later version.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 10 Version 1507 | 10.0.10240.0 up to, but not including, 10.0.10240.21161 | 10.0.10240.21161 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.8519 | 10.0.14393.8519 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.7919 | 10.0.17763.7919 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.6456 | 10.0.19044.6456 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.6456 | 10.0.19045.6456 |
| Microsoft | Windows 11 version 22H2 | 10.0.22621.0 up to, but not including, 10.0.22621.6060 | 10.0.22621.6060 |
| Microsoft | Windows 11 version 22H3 | 10.0.22631.0 up to, but not including, 10.0.22631.6060 | 10.0.22631.6060 |
| Microsoft | Windows 11 Version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.6060 | 10.0.22631.6060 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.6899 | 10.0.26100.6899 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.6899 | 10.0.26200.6899 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.8519 | 10.0.14393.8519 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.8519 | 10.0.14393.8519 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.7919 | 10.0.17763.7919 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.7919 | 10.0.17763.7919 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.4294 | 10.0.20348.4294 |
| Microsoft | Windows Server 2022, 23H2 Edition (Server Core installation) | 10.0.25398.0 up to, but not including, 10.0.25398.1913 | 10.0.25398.1913 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.6899 | 10.0.26100.6899 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.6899 | 10.0.26100.6899 |
| Microsoft | Windows 10 1507 | before 10.0.10240.21161 | 10.0.10240.21161 |
| Microsoft | Windows 10 1607 | before 10.0.14393.8519 | 10.0.14393.8519 |
| Microsoft | Windows 10 1809 | before 10.0.17763.7919 | 10.0.17763.7919 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.6456 | 10.0.19044.6456 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.6456 | 10.0.19045.6456 |
| Microsoft | Windows 11 22h2 | before 10.0.22621.6060 | 10.0.22621.6060 |
| Microsoft | Windows 11 23h2 | 10.0.22631.6060 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE; 3 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
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L. Scored by CNA (microsoft.com).
Official description
Concurrent execution using shared resource with improper synchronization ('race condition') in Data Sharing Service Client allows an unauthorized attacker to perform spoofing locally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
How developers prevent this class of flaw
- When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to inbox.txt and ID 2 could map to profile.txt. Features such as the ESAPI AccessReferenceMap provide this capability.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- 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.
More External Control of File Name or Path vulnerabilities (CWE-73)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Windows 10 Version 1507
- 7.0 High severity
- 7.8 High severity
- 7.0 High severity
- 7.0 High severity
Recent External Control of File Name or Path vulnerabilities
- 8.1 High severity
- 9.8 Critical severity
- 8.1 High severity
- 7.5 High severity
- 7.2 High severity
- 9.1 Critical severity
Spotted an error? Tell us.