CVE-2026-21519 Elastic Security · Elastic

Detect Microsoft Windows Type Confusion Vulnerability (CVE-2026-21519) in Elastic Security

Detects exploitation of CVE-2026-21519, a type confusion vulnerability (CWE-843) in Microsoft Windows. Type confusion vulnerabilities occur when code allocates or initializes a resource using one type but accesses it using an incompatible type, leading to out-of-bounds memory access, arbitrary code execution, or privilege escalation. This CVE is listed on the CISA Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild.

MITRE ATT&CK

Tactic
Privilege Escalation Defense Evasion Execution

Elastic Detection Query

Elastic Security (Elastic)
eql
sequence by host.name with maxspan=5m
  [process where event.type == "start"
   and (
     process.parent.name in ("lsass.exe", "winlogon.exe", "csrss.exe")
     and not process.name in~ ("conhost.exe", "werfault.exe", "WerFaultSecure.exe")
   )
  ] by process.entity_id
  [any where event.category == "driver"
   and event.action == "load"
   and not process.name in~ ("MsMpEng.exe", "services.exe", "wininit.exe", "TrustedInstaller.exe")
  ] by process.entity_id
| head 100
critical severity medium confidence

Elastic EQL sequence detection correlating anomalous child process spawning from protected system processes followed by driver load events initiated outside of trusted system processes, a pattern consistent with Windows type confusion exploitation.

Data Sources

Elastic SecurityWinlogbeatElastic Endpoint

Required Tables

logs-endpoint.events.process-*logs-endpoint.events.driver-*winlogbeat-*

False Positives & Tuning

  • Security software performing legitimate behavioral monitoring via kernel drivers
  • Hardware vendors installing kernel-mode drivers through unusual parent process chains
  • System administration tools using elevated process injection for legitimate management tasks
  • Virtualization software that spawns processes from system-level parent processes

Other platforms for CVE-2026-21519


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.

  1. Test 1Simulate Anomalous Child Process from Winlogon

    Expected signal: Sysmon EventID 1 showing cmd.exe or similar process with an unexpected parent, Windows Security EventID 4688 capturing the new process creation with command line arguments.

  2. Test 2Privilege Token Enumeration via Command Line

    Expected signal: Windows Security EventID 4688 with CommandLine containing privilege-related arguments, Sysmon EventID 1 capturing the full process creation with integrity level.

  3. Test 3Suspicious Service Installation from Temp Directory

    Expected signal: Windows System EventID 7045 (new service installed) with ServiceImagePath pointing to %TEMP%, Sysmon EventID 13 capturing registry writes for the new service key under HKLM\SYSTEM\CurrentControlSet\Services.

  4. Test 4Unsigned Driver Load Simulation via Sysmon

    Expected signal: Sysmon EventID 6 (DriverLoad) with the ImageLoaded path pointing to a non-standard location and the initiating process being a user-mode application rather than services.exe or wininit.exe.

Unlock Pro Content

Get the full detection package for CVE-2026-21519 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections