Skip to content
Server Security Center
KEVhigh8.8

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

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2026-02-10.

CVSS v3.1 (CVE record)
8.8
high
EPSS (exploit probability, 30 days)
61%
higher than 99.1% of all CVEs
Added to CISA KEV
2026-02-10
US federal due date 2026-03-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-21510 explained

CVE-2026-21510 is a protection mechanism failure in Windows Shell in Microsoft Windows. An unauthorized attacker can bypass a security feature over a network. It affects multiple Windows 10, Windows 11 and Windows Server releases, and CISA lists it as known to be exploited by attackers.

Impact

An unauthenticated attacker can bypass a Windows Shell security feature over the network. Attack complexity is low, but a user must take an action, such as interacting with attacker-supplied content. A successful attack can have high impact on confidentiality, integrity and availability. CISA rates the technical impact as total and says it is not automatable, so attacks require manual steps per target. CISA lists it as known exploited; ransomware use is unknown.

Who is affected

The CVE record lists Windows 10 Version 1607, 1809, 21H2 and 22H2; Windows 11 version 22H3, Version 23H2, 24H2, 25H2 and version 26H1; and Windows Server 2012 (including Server Core installation) and 2012 R2. Fixed builds include 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 and 6.3.9600.23022. Further products are listed on the page.

Written with AI from the data on this page and checked against it automatically.

Official description

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

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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.6937
    Fixed in
    • 10.0.19044.6937
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.6937
    Fixed in
    • 10.0.19045.6937
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.6649
    Fixed in
    • 10.0.22631.6649
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.6649
    Fixed in
    • 10.0.22631.6649
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.7840
    Fixed in
    • 10.0.26100.7840
  • Microsoft Windows 11 Version 25H2
    Affected
    • < 10.0.26200.7840
    Fixed in
    • 10.0.26200.7840
  • Microsoft Windows 11 version 26H1ARM64
    Affected
    • < 10.0.28000.1575
    Fixed in
    • 10.0.28000.1575
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25923
    Fixed in
    • 6.2.9200.25923
Show 11 more products
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25923
    Fixed in
    • 6.2.9200.25923
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.23022
    Fixed in
    • 6.3.9600.23022
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.23022
    Fixed in
    • 6.3.9600.23022
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.4773
    Fixed in
    • 10.0.20348.4773
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.2149
    Fixed in
    • 10.0.25398.2149
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.32370
    Fixed in
    • 10.0.26100.32370
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.32370
    Fixed in
    • 10.0.26100.32370

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1607: 10.0.14393.8868
    • Microsoft Windows 10 Version 1809: 10.0.17763.8389
    • Microsoft Windows 10 Version 21H2: 10.0.19044.6937
    • Microsoft Windows 10 Version 22H2: 10.0.19045.6937
    • Microsoft Windows 11 version 22H3: 10.0.22631.6649
    • Microsoft Windows 11 Version 23H2: 10.0.22631.6649
    Fixed versions for 15 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21510
  • CISA's deadline for US federal agencies: 2026-03-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version, for example 10.0.26100.7840 for Windows 11 Version 24H2.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited; US federal agencies must remediate by 2026-03-03.
  3. Follow the Microsoft advisory for any additional mitigations or guidance.
  4. Warn users against opening untrusted files or links, since exploitation requires user interaction.
  5. Check systems for signs of compromise, especially those that remained unpatched.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-693 Protection Mechanism Failure

Questions about CVE-2026-21510

Is CVE-2026-21510 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-02-10. Whether it has been used in ransomware campaigns is unknown.
Does an attacker need credentials?
No. The attacker needs no privileges, but a user must interact for the attack to succeed. CISA rates it as not automatable.
What should I do if I cannot patch immediately?
CISA's required action is to apply mitigations per vendor instructions, follow BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.