CVE-2026-105545Microsoft Windows 10 race condition
CVE-2026-105545 is a race condition in Microsoft Windows 10, rated high (7.0 on CVSS 3.1).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Awaiting Analysis
What it is
Two operations race on shared state, and an attacker who wins the race bypasses a check or corrupts data. Memory is freed twice, which can corrupt the heap and lead to code execution.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user 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 read the data it protects, change data or behaviour and take it offline. 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.
What to do
- Apply the update for your edition of Microsoft Windows 10. Fixed builds: Windows 10 Version 1607: 10.0.14393.9612; Windows 10 Version 1809: 10.0.17763.9376; Windows 10 Version 21H2: 10.0.19044.7807; Windows 10 Version 22H2: 10.0.19045.7807. Other affected products have their own fixed versions on this page.
- Limit who can run code or sign in on the hosts that run it.
Description from NVD
An elevation of privilege vulnerability exists in the Windows Installer when the Windows Installer fails to properly sanitize input leading to an insecure library loading behavior. A locally authenticated attacker could run arbitrary code with elevated system privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. The security update addresses the vulnerability by correcting the input sanitization error to preclude unintended elevation.
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.
- Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
- Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- Between concurrent requests or processes. An attacker who crosses it can win a timing window to bypass a check or corrupt shared state.
- Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.
Questions to answer about your own systems
- Where does Microsoft Windows 10 run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- 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.