LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21510: Windows Shell Security Feature Bypass Vulnerability

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

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Windows Shell security feature bypass that can be triggered over a network if a user interacts with malicious content. Microsoft rates it high severity, and CISA KEV indicates known exploitation. Business urgency is high for Windows endpoints and servers listed by Microsoft.

Executive priority

Prioritize remediation promptly because this is high severity, affects broad Windows fleets, and is listed by CISA as known exploited. The main management task is patch assurance across endpoints and servers, not speculative investigation of unconfirmed exploit details.

Technical view

CVE-2026-21510 is CWE-693 protection mechanism failure in Windows Shell. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, required user interaction, and high confidentiality, integrity, and availability impact. Microsoft lists official remediation availability.

Likely exposure

Exposure is likely wherever affected Windows 10, Windows 11, or Windows Server versions are still present and not remediated. User interaction is required, so workstations, shared desktops, and servers used for browsing or opening network-delivered content deserve priority review.

Exploitation context

CISA KEV status supports that this vulnerability has been exploited in the wild. The provided sources do not describe exploit methods, campaigns, payloads, or victim sectors. Treat exploitation evidence as real but operational detail as incomplete.

Researcher notes

The bundle confirms network reachability, no required privileges, user interaction required, and high impact across CIA. It does not provide root cause detail, affected Shell components, exploit primitives, indicators, or workaround specifics beyond Microsoft remediation availability.

Mitigation direction

  • Apply Microsoft guidance and security updates for CVE-2026-21510.
  • Prioritize affected Windows endpoints and interactive servers first.
  • Confirm managed patch policies cover listed Windows 10, 11, and Server releases.
  • Restrict unnecessary user interaction on servers until patched.
  • Monitor CISA KEV and MSRC for updated remediation instructions.

Validation and detection

  • Inventory Windows builds against Microsoft’s affected product list.
  • Verify the relevant Microsoft security update is installed.
  • Check exception lists for devices missing February 2026 or later remediation.
  • Confirm Server Core systems are included in patch compliance reporting.
  • Review exposure of shared desktops and servers used interactively.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-693: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21510 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C2.85.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-21510Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  3. ADP timelineCISA-ADP

    CVE-2026-21510 added to CISA KEV

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvcother:kev
  • 2026-02-10T00:00:00.000Z: CVE-2026-21510 added to CISA KEV

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 21H210.0.19044.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 22H310.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 24H210.0.26100.0Listed
MicrosoftWindows 11 Version 25H210.0.26200.0Listed
MicrosoftWindows 11 version 26H110.0.28000.0Listed
MicrosoftWindows 11 Version 26H110.0.28000.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
MicrosoftWindows Server 202510.0.26100.0Listed
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-693 · source CWE mapping

Protection Mechanism Failure

Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.