Windows 10 Version 1607: Incorrect Permission Assignment for Critical Resource
CVE-2026-24291 is a high-severity incorrect permission assignment for critical resource 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.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 4.61% chance of exploitation within 30 days, which is in the top 8.18% of all scored 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
- 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
Incorrect permission assignment for critical resource in Windows Accessibility Infrastructure (ATBroker.exe) 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: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
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 Incorrect Permission Assignment for Critical Resource vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.4 High severity
Spotted an error? Tell us.