CVE-2026-21525

CVE-2026-21525 - Microsoft Windows NULL Pointer Dereference Exploitation

Detects exploitation attempts and post-exploitation activity related to CVE-2026-21525, a NULL pointer dereference vulnerability in Microsoft Windows. This vulnerability is actively exploited in the wild (CISA KEV) and may allow attackers to achieve privilege escalation or code execution via memory corruption techniques targeting Windows kernel or user-mode components.

Vulnerability Intelligence

KEV — Known Exploited

Affected Software

Vendor
Microsoft
Product
Windows

Weakness (CWE)

Timeline

Disclosed
February 10, 2026

CVSS

Unscored
Write-up coming soon

What is CVE-2026-21525 CVE-2026-21525 - Microsoft Windows NULL Pointer Dereference Exploitation?

CVE-2026-21525 - Microsoft Windows NULL Pointer Dereference Exploitation (CVE-2026-21525) maps to the Privilege Escalation and Defense Evasion and Execution tactics — the adversary is trying to gain higher-level permissions in MITRE ATT&CK.

This page provides production-ready detection logic for CVE-2026-21525 - Microsoft Windows NULL Pointer Dereference Exploitation, covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, Windows Security Events, Windows Application Event Log. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Privilege Escalation Defense Evasion Execution
Microsoft Sentinel / Defender
kusto
let timeframe = 24h;
let suspiciousProcesses = dynamic(["lsass.exe", "svchost.exe", "csrss.exe", "winlogon.exe"]);
union SecurityEvent, DeviceProcessEvents, DeviceEvents
| where TimeGenerated >= ago(timeframe)
| where ActionType in ("ProcessCreated", "ProcessCrashed", "KernelDriverLoaded") or EventID in (1001, 1000, 41)
| where (FileName in~ (suspiciousProcesses) and (ProcessCommandLine contains "null" or ProcessCommandLine contains "0x00000000"))
    or (ActionType == "ProcessCrashed" and FileName in~ (suspiciousProcesses))
    or (EventID == 1001 and (ApplicationName has_any (suspiciousProcesses)))
| extend RiskScore = case(
    ActionType == "ProcessCrashed" and FileName =~ "lsass.exe", 100,
    ActionType == "KernelDriverLoaded" and InitiatingProcessIntegrityLevel != "System", 80,
    EventID == 1001, 60,
    50)
| where RiskScore >= 50
| project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, ActionType, EventID, RiskScore
| sort by RiskScore desc, TimeGenerated desc

Detects process crashes, kernel driver loads, and Windows Error Reporting events consistent with NULL pointer dereference exploitation targeting Windows system processes. Focuses on LSASS, SVCHOST and other high-value processes crashing or loading unexpected drivers.

high severity medium confidence

Data Sources

Microsoft Defender for Endpoint Windows Security Events Windows Application Event Log

Required Tables

SecurityEvent DeviceProcessEvents DeviceEvents

False Positives

  • Legitimate application crashes due to software bugs unrelated to exploitation
  • Antivirus or EDR products performing kernel-level inspection that may trigger driver load events
  • System updates or patches that temporarily cause process instability
  • Memory dumps or diagnostic tools running during incident response activities

Sigma rule & cross-platform mapping

The detection logic for CVE-2026-21525 - Microsoft Windows NULL Pointer Dereference Exploitation (CVE-2026-21525) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: process_creation
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 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 Windows Process Crash via WER Trigger

    Expected signal: EventID 1001 in Windows Application Event Log with FaultingApplicationName=CrashTest.exe and ExceptionCode=C0000005; Sysmon EventID 1 for process creation; EDR process termination event with non-zero exit code

  2. Test 2Load Unsigned Test Driver to Simulate Kernel Exploitation Activity

    Expected signal: EventID 7045 in Windows System Event Log with ServiceName=CVE202621525TestDriver and ServiceType=kernel mode driver; Sysmon EventID 12/13 for registry modifications under HKLM\SYSTEM\CurrentControlSet\Services

  3. Test 3LSASS Access Simulation via ProcDump

    Expected signal: Sysmon EventID 10 (ProcessAccess) with TargetImage=lsass.exe and GrantedAccess including 0x1FFFFF or 0x1010; Windows Defender EventID 1121 if credential protection rules are enabled; EDR LSASS access alert

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections