Detect CVE-2026-21510: Microsoft Windows Shell Protection Mechanism Failure in CrowdStrike LogScale
Detects exploitation of CVE-2026-21510, a Microsoft Windows Shell protection mechanism failure (CWE-693) that allows attackers to bypass security controls enforced by the Windows Shell. This vulnerability is actively exploited in the wild (CISA KEV). Attackers may abuse this flaw to execute unauthorized code, bypass security prompts, or escalate privileges via crafted shell interactions.
MITRE ATT&CK
LogScale Detection Query
#event_simpleName=ProcessRollup2
| ParentBaseFileName in ("winlogon.exe", "services.exe", "svchost.exe", "lsass.exe", "csrss.exe")
AND FileName in ("explorer.exe", "cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe")
| OR (
FileName = "explorer.exe"
AND (CommandLine = "*/factory*" OR CommandLine = "*-Embedding*")
AND ParentBaseFileName != "userinit.exe"
)
| eval RiskLevel = if(ParentBaseFileName in ("lsass.exe", "csrss.exe"), "CRITICAL", "HIGH")
| table timestamp, ComputerName, UserName, ParentBaseFileName, FileName, CommandLine, ParentCommandLine, TargetProcessId, ContextProcessId, RiskLevel
| sort - timestampCrowdStrike Falcon LogScale (CQL) query on ProcessRollup2 events to detect Windows Shell spawning from privileged system processes and anomalous explorer.exe instantiation, consistent with CVE-2026-21510 shell protection bypass exploitation.
Data Sources
Required Tables
False Positives & Tuning
- CrowdStrike sensor itself or Falcon-managed scripts that interact with shell from service context
- IT automation platforms (e.g., Ansible, Puppet) deploying software via Windows service accounts
- Explorer.exe restarted by Windows Error Reporting or crash recovery mechanisms
- Legitimate COM activation via -Embedding for registered shell namespace extensions
Other platforms for CVE-2026-21510
Testing Methodology
Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulate Shell Spawn from Winlogon Context
Expected signal: Sysmon Event ID 1: cmd.exe process with ParentImage path containing winlogon.exe or SYSTEM session identifier; Windows Security Event 4688 showing cmd.exe process creation under SYSTEM account.
- Test 2Explorer.exe Factory Flag Instantiation
Expected signal: Sysmon Event ID 1: explorer.exe process with CommandLine containing /factory and ParentImage of powershell.exe; corresponding network or registry activity from the new explorer instance.
- Test 3PowerShell Encoded Command via Shell Bypass Chain
Expected signal: Sysmon Event ID 1: powershell.exe with -EncodedCommand in CommandLine, parent cmd.exe; Sysmon Event ID 3: any outbound connection if payload includes network activity.
- Test 4Shell Bypass Followed by Discovery Commands
Expected signal: Sysmon Event IDs 1 for cmd.exe (parent: psexec/SYSTEM), then whoami.exe and ipconfig.exe as children within 30 seconds; all events share the same host identifier.
Unlock Pro Content
Get the full detection package for CVE-2026-21510 including response playbook, investigation guide, and atomic red team tests.