CVE-2026-21510: Microsoft Windows Shell Protection Mechanism Failure Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Protection mechanism failure in Windows Shell allows an unauthorized attacker to bypass a security feature over a network.

Description quoted from the CVE record (assigned by microsoft, published 2026-02-10).

Weakness: CWE-693: Protection Mechanism Failure

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since
2026-02-10
US federal deadline
2026-03-03
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-01630, EUVD-2026-7337, GHSA-q6v4-4w5r-j7hr

Exploit Observer links 1 piece of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (1)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (1)

Vulnerability databases and vendor advisories (6)

Catalogue entries, not exploit evidence.

19 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.612
very likely to be attacked soon
VEDAS
0.658
some exploit evidence
On CISA KEV
Yes, since 2026-02-10
Detection rule
None yet
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2026-21510 EPSS over time2026-022026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9CVE-2026-21510 VEDAS over time2026-022026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.8868Not stated
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.8389Not stated
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.6937Not stated
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.6937Not stated
Microsoft Windows 11 version 22H3from 10.0.22631.0 before 10.0.22631.6649Not stated
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.6649Not stated
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.7840Not stated
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.7840Not stated
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.1575Not stated
Microsoft Windows 11 Version 26H1from 10.0.28000.0 before 10.0.28000.1575Not stated
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.25923Not stated
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.25923Not stated
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.23022Not stated
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.23022Not stated
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.8868Not stated
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.8868Not stated
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.8389Not stated
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.8389Not stated
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.4773Not stated
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)from 10.0.25398.0 before 10.0.25398.2149Not stated

2 more products are listed in the CVE record.

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: microsoft windows_10_1607, microsoft windows_10_1809, microsoft windows_10_21h2, microsoft windows_10_22h2, microsoft windows_11_23h2, microsoft windows_11_24h2, microsoft windows_11_25h2, microsoft windows_server_2012, microsoft windows_server_2016, microsoft windows_server_2019.

How to fix it

Fixed versions stated in the CVE record: 10.0.14393.8868, 10.0.17763.8389, 10.0.19044.6937, 10.0.19045.6937, 10.0.22631.6649, 10.0.26100.7840, 10.0.26200.7840, 10.0.28000.1575, 6.2.9200.25923, 6.3.9600.23022, 10.0.20348.4773, 10.0.25398.2149 and others.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Vendor guidance:

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

References

Vendor advisories and patches

Government sources

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.