CVE-2026-122474Microsoft Windows 10 time-of-check to time-of-use race
CVE-2026-122474 is a time-of-check to time-of-use race in Microsoft Windows 10, rated medium (5.9 on CVSS 3.1).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Awaiting Analysis
What it is
Something is checked, then changed by an attacker before it is used.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker win a timing window to bypass a check or corrupt shared state.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.54% chance of exploitation activity in the next 30 days, higher than 46% of scored CVEs.
What to do
- Apply the update for your edition of Microsoft Windows 10. Fixed builds: Windows 10 Version 1607: 10.0.14393.9688; Windows 10 Version 1809: 10.0.17763.9487; Windows 10 Version 21H2: 10.0.19044.7846; Windows 10 Version 22H2: 10.0.19045.7846. Other affected products have their own fixed versions on this page.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
Time-of-check time-of-use (toctou) race condition in Windows Security Account Manager allows an unauthorized attacker to bypass a security feature over a network.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Request handlers and jobs that share state. The flaw sits between concurrent requests or processes.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Between concurrent requests or processes. An attacker who crosses it can win a timing window to bypass a check or corrupt shared state.
Questions to answer about your own systems
- Where does Microsoft Windows 10 run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.