CVE-2026-85880

CVE-2026-85880: Microsoft Windows Heap-Based Buffer Overflow Exploitation

Privilege Escalation Execution Last updated:

Detects exploitation attempts and post-exploitation activity associated with CVE-2026-85880, a heap-based buffer overflow (CWE-122) with use of uninitialized resource (CWE-908) in Microsoft Windows. Listed in the CISA KEV catalog (disclosed 2026-09-08), this vulnerability is actively exploited to achieve memory corruption leading to elevation of privilege or remote code execution. Detection focuses on process crash telemetry (WER/faulting module), anomalous child processes spawned from Windows components, suspicious memory operations, and privilege-escalation indicators following a crash, since no public PoC or specific affected-version list is available and exploitation manifests primarily as crash-then-execute behavior.

Vulnerability Intelligence

KEV — Known Exploited

What is CVE-2026-85880 CVE-2026-85880: Microsoft Windows Heap-Based Buffer Overflow Exploitation?

CVE-2026-85880: Microsoft Windows Heap-Based Buffer Overflow Exploitation (CVE-2026-85880) maps to the Privilege Escalation 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-85880: Microsoft Windows Heap-Based Buffer Overflow Exploitation, covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, DeviceProcessEvents, DeviceEvents. 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 Execution
Microsoft Sentinel / Defender
kusto
let suspiciousChildren = dynamic(["cmd.exe","powershell.exe","rundll32.exe","regsvr32.exe","mshta.exe","wscript.exe","cscript.exe"]);
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName has_any ("svchost.exe","services.exe","lsass.exe","spoolsv.exe","dwm.exe","csrss.exe")
| where FileName in~ (suspiciousChildren)
| where InitiatingProcessIntegrityLevel in~ ("System","High")
| project Timestamp, DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine, InitiatingProcessIntegrityLevel, AccountName
| join kind=leftouter (
    DeviceEvents
    | where Timestamp > ago(24h)
    | where ActionType == "ProcessCrashDetected" or ActionType == "AppCrash"
    | project DeviceName, CrashTime=Timestamp, FaultingModule=AdditionalFields
) on DeviceName
| where isempty(CrashTime) or abs(datetime_diff('second', Timestamp, CrashTime)) < 120
| project Timestamp, DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine, AccountName, InitiatingProcessIntegrityLevel

Identifies suspicious child processes (shells, LOLBins) spawned by core Windows service processes at System/High integrity, optionally correlated with a nearby process crash — a common footprint of heap-overflow exploitation of a privileged Windows component per CVE-2026-85880.

high severity medium confidence

Data Sources

Microsoft Defender for Endpoint DeviceProcessEvents DeviceEvents

Required Tables

DeviceProcessEvents DeviceEvents

False Positives

  • Legitimate administrative scripts launched by scheduled tasks running as SYSTEM
  • Software deployment agents (SCCM, Intune) invoking cmd/powershell from service context
  • Backup or monitoring agents spawning shells from privileged service processes

Sigma rule & cross-platform mapping

The detection logic for CVE-2026-85880: Microsoft Windows Heap-Based Buffer Overflow Exploitation (CVE-2026-85880) 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 privileged service spawning a shell

    Expected signal: ProcessRollup2 / DeviceProcessEvents record showing cmd.exe spawned at SYSTEM integrity from a service context.

  2. Test 2Generate an application crash event

    Expected signal: Application event log EventCode 1000 and a WER crash dump for the faulting process.

  3. Test 3LOLBin spawned from service context

    Expected signal: Process-creation telemetry showing rundll32.exe launched from a service (services.exe) parent at SYSTEM integrity.


Response Playbook

Triage

  1. Confirm the alerting host is a Windows system and identify whether the parent service process (svchost/services/lsass/spoolsv) crashed shortly before the child process was spawned by reviewing WER and EventCode 1000 records.
  2. Determine the Windows build/patch level and cross-reference against the MSRC advisory for CVE-2026-85880 to confirm whether the host is missing the fix.
  3. Examine the spawned child process command line, parent lineage, and integrity level to assess whether execution occurred at System/High privilege.
  4. Check for concurrent authentication anomalies (new admin sessions, token manipulation) that would indicate successful privilege escalation.

Containment

  1. Isolate the affected host from the network via EDR containment to prevent lateral movement while preserving volatile evidence.
  2. Suspend or terminate the suspicious child process tree and disable any persistence (services, scheduled tasks, run keys) created after the crash.
  3. Force a credential reset for accounts that were active on the host, prioritizing privileged/service accounts if System-level execution is confirmed.

Evidence Collection

  1. Capture a full memory image and the WER crash dumps for the faulting Windows component before rebooting to preserve heap-corruption artifacts.
  2. Collect Sysmon/EDR process telemetry, Application event log crash records, and the child-process command lines and dropped files for the incident window.
  3. Export scheduled tasks, services, and autorun entries created or modified around the crash timestamp.

Escalation Criteria

  • ! Escalate to incident response immediately if child-process execution is confirmed at SYSTEM integrity following a service crash.
  • ! Escalate to threat-intel/vulnerability management if the host is confirmed unpatched against CVE-2026-85880 given its active-exploitation (KEV) status.
  • ! Escalate to CISO/legal if privileged credential compromise or lateral movement from the host is identified.

Investigation Guide

Forensic Artifacts

  • > Windows Error Reporting (WER) crash dumps and ReportArchive entries for the faulting Windows module
  • > Application event log EventCode 1000 records naming the faulting application and module
  • > Sysmon/EDR process-creation records linking the crashed service to an anomalous child process

Tuning Guidance

Build a per-environment allowlist of legitimate SYSTEM-context automation (SCCM/Intune, backup and monitoring agents) that spawn shells from service processes, and exclude those parent/child/command-line combinations. Tighten confidence by requiring correlation with a nearby crash event (EventCode 1000) where crash telemetry is reliably collected, and consider raising severity to critical on servers exposed to untrusted input.


Hunting Queries

Baselines which child processes are normally spawned by core Windows service processes so anomalies from CVE-2026-85880 exploitation stand out.

Hunting — KQL
kql
DeviceProcessEvents | where InitiatingProcessFileName in~ ("svchost.exe","services.exe","lsass.exe","spoolsv.exe") | where InitiatingProcessIntegrityLevel in~ ("System","High") | summarize count() by FileName, InitiatingProcessFileName, DeviceName | order by count_ desc
Hunting — SPL
spl
index=windows sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 (ParentImage="*svchost.exe" OR ParentImage="*services.exe" OR ParentImage="*lsass.exe") | stats count by Image, ParentImage, host

Atomic Red Team Tests

Test 1 Simulate privileged service spawning a shell
windows

Uses PsExec to launch cmd.exe as SYSTEM to emulate the post-exploitation footprint of a heap overflow in a privileged Windows service.

Command

powershell
psexec.exe -accepteula -s -i cmd.exe /c "whoami > C:\Windows\Temp\cve_2026_85880_test.txt"

Cleanup

powershell
del C:\Windows\Temp\cve_2026_85880_test.txt

Expected Telemetry

ProcessRollup2 / DeviceProcessEvents record showing cmd.exe spawned at SYSTEM integrity from a service context.

Expected Detection

KQL and CQL rules flag the System-integrity shell launch from a service parent.

Test 2 Generate an application crash event
windows

Forces a benign application crash to produce a WER dump and EventCode 1000 record, exercising the crash-correlation logic.

Command

powershell
powershell -c "$p = Start-Process notepad -PassThru; Start-Sleep 2; Stop-Process -Id $p.Id -Force; [void](Add-Type -MemberDefinition 'public static void C(){throw new System.AccessViolationException();}' -Name X -Namespace Y -PassThru)"

Cleanup

powershell
Remove-Item "$env:LOCALAPPDATA\Microsoft\Windows\WER\ReportArchive\*" -Recurse -Force -ErrorAction SilentlyContinue

Expected Telemetry

Application event log EventCode 1000 and a WER crash dump for the faulting process.

Expected Detection

SPL and QRadar rules match the EventCode 1000 crash event within the correlation window.

Test 3 LOLBin spawned from service context
windows

Runs rundll32.exe from a SYSTEM service context to emulate code execution following memory corruption.

Command

powershell
sc create cve85880test binPath= "cmd.exe /c rundll32.exe C:\Windows\System32\shell32.dll,Control_RunDLL" start= demand & sc start cve85880test

Cleanup

powershell
sc stop cve85880test & sc delete cve85880test

Expected Telemetry

Process-creation telemetry showing rundll32.exe launched from a service (services.exe) parent at SYSTEM integrity.

Expected Detection

Elastic EQL, Chronicle YARA-L and CrowdStrike CQL rules flag the LOLBin spawned from a privileged service parent.

Related Detections