Windows 10 Version 1607: Improper Validation of Specified Type of Input
CVE-2026-25179 is a high-severity improper validation of specified type of input vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 7.0 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.8957 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.36% 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.8957 or a later version.
- Update Windows 10 Version 1809 to 10.0.17763.8511 or a later version.
- Update Windows 10 Version 21H2 to 10.0.19044.7058 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.8957 | 10.0.14393.8957 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.8511 | 10.0.17763.8511 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.7058 | 10.0.19044.7058 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.7058 | 10.0.19045.7058 |
| Microsoft | Windows 11 version 22H3 | 10.0.22631.0 up to, but not including, 10.0.22631.6783 | 10.0.22631.6783 |
| Microsoft | Windows 11 Version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.6783 | 10.0.22631.6783 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.8037 | 10.0.26100.8037 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.8037 | 10.0.26200.8037 |
| Microsoft | Windows 11 version 26H1 | 10.0.28000.0 up to, but not including, 10.0.28000.1719 | 10.0.28000.1719 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.25973 | 6.2.9200.25973 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.25973 | 6.2.9200.25973 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.23074 | 6.3.9600.23074 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.23074 | 6.3.9600.23074 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.8957 | 10.0.14393.8957 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.8957 | 10.0.14393.8957 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.8511 | 10.0.17763.8511 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.8511 | 10.0.17763.8511 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.4893 | 10.0.20348.4893 |
| Microsoft | Windows Server 2022, 23H2 Edition (Server Core installation) | 10.0.25398.0 up to, but not including, 10.0.25398.2207 | 10.0.25398.2207 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.32522 | 10.0.26100.32522 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.32522 | 10.0.26100.32522 |
| Microsoft | Windows 10 1607 | before 10.0.14393.8957 | 10.0.14393.8957 |
| Microsoft | Windows 10 1809 | before 10.0.17763.8511 | 10.0.17763.8511 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.7058 | 10.0.19044.7058 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.7058 | 10.0.19045.7058 |
Version data comes from the organisation that assigned the CVE; 5 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
- HighSuccess depends on conditions outside the attacker's control.
- 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:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Improper validation of specified type of input in Windows Ancillary Function Driver for WinSock 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 Validation of Specified Type of Input
The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
More Improper Validation of Specified Type of Input vulnerabilities (CWE-1287)
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 Validation of Specified Type of Input vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 7.4 High severity
- 9.1 Critical severity
- 7.7 High severity
- 7.2 High severity
Spotted an error? Tell us.