CVE-2026-21510Microsoft Windows Shell Protection Mechanism Failure Vulnerability
CVE-2026-21510 is a protection mechanism failure in Microsoft Windows, rated high (8.8 on CVSS 3.1).
Why this priority: Exploited in the wild: listed in CISA's KEV catalog.
Published · Updated · NVD status: Analyzed
What it is
A security control can be bypassed or does not work as intended.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.
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 use a weak default the deployment never changed.
Is it being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 2026-02-10: it is being exploited in the wild. EPSS estimates a 61% chance of exploitation activity in the next 30 days, higher than 99% of scored CVEs.
What to do
- Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-03-03.
- Apply the update for your edition of Microsoft Windows. Fixed builds: Windows 10 Version 1607: 10.0.14393.8868; Windows 10 Version 1809: 10.0.17763.8389; Windows 10 Version 21H2: 10.0.19044.6937; Windows 10 Version 22H2: 10.0.19045.6937; Windows 11 version 22H3: 10.0.22631.6649; Windows 11 Version 23H2: 10.0.22631.6649; and 15 more on this page.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
- Check exposed instances for signs of compromise, not only for the version.
Description from NVD
Protection mechanism failure in Windows Shell 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
- Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
- Default settings, permissions and deployment configuration. The flaw sits between the shipped defaults and a hardened deployment.
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.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between the shipped defaults and a hardened deployment. An attacker who crosses it can use a weak default the deployment never changed.
Questions to answer about your own systems
- Where does Microsoft Windows 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.