Windows 10 Version 1607: Use of Uninitialized Resource
CVE-2026-85322 is a high-severity use of uninitialized resource vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 10.0.14393.9612 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 1.03% chance of exploitation within 30 days, higher than 64% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Windows 10 Version 1607 to 10.0.14393.9612 or a later version.
- Update Windows 10 Version 1809 to 10.0.17763.9376 or a later version.
- Update Windows 10 Version 21H2 to 10.0.19044.7807 or a later version.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
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.9612 | 10.0.14393.9612 |
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.7807 | 10.0.19044.7807 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.7807 | 10.0.19045.7807 |
| Microsoft | Windows 11 version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.7652 | 10.0.22631.7652 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.9711 | 10.0.26100.9711 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.9711 | 10.0.26200.9711 |
| Microsoft | Windows 11 version 26H1 | 10.0.28000.0 up to, but not including, 10.0.28000.3231 | 10.0.28000.3231 |
| Microsoft | Windows 11 Version 26H2 | 10.0.26300.0 up to, but not including, 10.0.26300.9711 | 10.0.26300.9711 |
| Microsoft | Windows Server 2012 | 6.2.9200.0 up to, but not including, 6.2.9200.26434 | 6.2.9200.26434 |
| Microsoft | Windows Server 2012 (Server Core installation) | 6.2.9200.0 up to, but not including, 6.2.9200.26434 | 6.2.9200.26434 |
| Microsoft | Windows Server 2012 R2 | 6.3.9600.0 up to, but not including, 6.3.9600.23470 | 6.3.9600.23470 |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | 6.3.9600.0 up to, but not including, 6.3.9600.23470 | 6.3.9600.23470 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.9612 | 10.0.14393.9612 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.9612 | 10.0.14393.9612 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.5761 | 10.0.20348.5761 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.33650 | 10.0.26100.33650 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.33650 | 10.0.26100.33650 |
| Microsoft | Windows 10 1607 | before 10.0.14393.9612 | 10.0.14393.9612 |
| Microsoft | Windows 10 1809 | before 10.0.17763.9376 | 10.0.17763.9376 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.7807 | 10.0.19044.7807 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.7807 | 10.0.19045.7807 |
| Microsoft | Windows 11 23h2 | before 10.0.22631.7652 | 10.0.22631.7652 |
Version data comes from the organisation that assigned the CVE; 4 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- 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
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CNA (microsoft.com).
Official description
Use of uninitialized resource in Windows Routing and Remote Access Service (RRAS) allows an unauthorized attacker to disclose information over a network.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Uninitialized Resource
The product uses or accesses a resource that has not been initialized.
How developers prevent this class of flaw
- Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
- Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
- Avoid race conditions (CWE-362) during initialization routines.
More Use of Uninitialized Resource vulnerabilities (CWE-908)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Recent Use of Uninitialized Resource vulnerabilities
- 9.6 Critical severity
- 7.1 High severity
- 7.1 High severity
- 7.8 High severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.