Windows 10 Version 1607: Improper Control of Generation of Code
CVE-2026-83759 is a high-severity improper control of generation of code vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, 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 0.92% chance of exploitation within 30 days, higher than 61% 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.
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 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 |
| Microsoft | Windows 11 24h2 | before 10.0.26100.9711 | 10.0.26100.9711 |
| Microsoft | Windows 11 25h2 | before 10.0.26200.9711 | 10.0.26200.9711 |
| Microsoft | Windows 11 26h1 | before 10.0.28000.3231 | 10.0.28000.3231 |
| Microsoft | Windows 11 26h2 | before 10.0.26300.9711 | 10.0.26300.9711 |
Version data comes from the organisation that assigned the CVE. 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
- 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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Improper control of generation of code ('code injection') in Windows Encrypting File System (EFS) allows an authorized attacker to execute code over a network.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- 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 which code can be executed by your product. 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.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
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 Control of Generation of Code vulnerabilities
- 10.0 Critical severity
- 9.1 Critical severity
- 9.9 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.