Windows 10 Version 21H2: Time-of-check Time-of-use (TOCTOU) Race Condition
CVE-2026-45487 is a high-severity time-of-check time-of-use (TOCTOU) race condition vulnerability in Windows 10 Version 21H2 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.19044.7417 as the first without the flaw, so updating Windows 10 Version 21H2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% 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 21H2 to 10.0.19044.7417 or a later version.
- Update Windows 10 Version 22H2 to 10.0.19045.7417 or a later version.
- Update Windows 11 version 23H2 to 10.0.22631.7219 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 21H2 | 10.0.19044.0 up to, but not including, 10.0.19044.7417 | 10.0.19044.7417 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.7417 | 10.0.19045.7417 |
| Microsoft | Windows 11 version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.7219 | 10.0.22631.7219 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.8655 | 10.0.26100.8655 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.8655 | 10.0.26200.8655 |
| Microsoft | Windows 11 version 26H1 | 10.0.28000.0 up to, but not including, 10.0.28000.2269 | 10.0.28000.2269 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.5256 | 10.0.20348.5256 |
| Microsoft | Windows Server 2025 | 10.0.26100.0 up to, but not including, 10.0.26100.32995 | 10.0.26100.32995 |
| Microsoft | Windows Server 2025 (Server Core installation) | 10.0.26100.0 up to, but not including, 10.0.26100.32995 | 10.0.26100.32995 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.7417 | 10.0.19044.7417 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.7417 | 10.0.19045.7417 |
| Microsoft | Windows 11 23h2 | before 10.0.22631.7219 | 10.0.22631.7219 |
| Microsoft | Windows 11 24h2 | before 10.0.26100.8655 | 10.0.26100.8655 |
| Microsoft | Windows 11 25h2 | before 10.0.26200.8655 | 10.0.26200.8655 |
| Microsoft | Windows 11 26h1 | before 10.0.28000.2269 | 10.0.28000.2269 |
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
- 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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA (microsoft.com) |
| CVSS 3.1 | 7.0 | High | NVD |
Official description
Time-of-check time-of-use (TOCTOU) race condition in Program Compatibility Assistant Service 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: Time-of-check Time-of-use (TOCTOU) Race Condition
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
How developers prevent this class of flaw
- The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
- When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
- Limit the interleaving of operations on files from multiple processes.
More Time-of-check Time-of-use (TOCTOU) Race Condition vulnerabilities (CWE-367)
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 Time-of-check Time-of-use (TOCTOU) Race Condition vulnerabilities
- 8.1 High severity
- 7.3 High severity
- 7.3 High severity
- 7.4 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.