CVE-2026-96951

Microsoft Windows Command Injection (CVE-2026-96951)

Initial Access Execution Last updated:

Detects exploitation of CVE-2026-96951, a command injection vulnerability (CWE-77) in Microsoft Windows that is listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation allows an attacker to inject and execute arbitrary operating-system commands via improperly neutralized special elements passed to a Windows component. This detection surfaces suspicious child-process chains, shell invocations with injected command separators/metacharacters, and anomalous process lineage consistent with active exploitation on unpatched hosts.

Vulnerability Intelligence

KEV — Known Exploited

Affected Software

Vendor
Microsoft
Product
Windows

Weakness (CWE)

Timeline

Disclosed
October 13, 2026

CVSS

Unscored
CVSS vector not yet published
Write-up coming soon

What is CVE-2026-96951 Microsoft Windows Command Injection (CVE-2026-96951)?

Microsoft Windows Command Injection (CVE-2026-96951) (CVE-2026-96951) maps to the Initial Access and Execution tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for Microsoft Windows Command Injection (CVE-2026-96951), covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, DeviceProcessEvents. 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
Initial Access Execution
Microsoft Sentinel / Defender
kusto
DeviceProcessEvents
| where Timestamp > ago(7d)
| where InitiatingProcessFileName in~ ("svchost.exe", "services.exe", "spoolsv.exe", "w3wp.exe", "wsmprovhost.exe", "explorer.exe")
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe")
| where ProcessCommandLine has_any ("&", "|", ";", "&&", "||", "`", "$(", "%0a", "\n")
| where ProcessCommandLine has_any ("whoami", "net ", "certutil", "bitsadmin", "curl ", "Invoke-WebRequest", "-enc", "FromBase64String", "rundll32", "regsvr32")
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, FileName, ProcessCommandLine, ProcessId, InitiatingProcessCommandLine
| order by Timestamp desc

Flags shell interpreters spawned by typically non-interactive service/host processes with command-line content containing shell metacharacters and reconnaissance/download tooling, consistent with CVE-2026-96951 command injection.

high severity medium confidence

Data Sources

Microsoft Defender for Endpoint DeviceProcessEvents

Required Tables

DeviceProcessEvents

False Positives

  • Legitimate administrative scripts invoking cmd/powershell with pipes or chained commands
  • Software deployment and configuration-management agents (SCCM, Ansible) running chained commands
  • Monitoring or backup tooling that legitimately spawns shells from service hosts

Sigma rule & cross-platform mapping

The detection logic for Microsoft Windows Command Injection (CVE-2026-96951) (CVE-2026-96951) 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 1 Shell command chaining via metacharacter injection

    Expected signal: Sysmon EventID 1 / Security 4688 showing cmd.exe with a command line containing '&' separators and whoami/net invocations.

  2. Test 2 PowerShell encoded command via pipe injection

    Expected signal: Process-creation event for powershell.exe with command line containing '|' and '-enc' with a base64 blob.

  3. Test 3 Service-host spawned download via certutil

    Expected signal: cmd.exe process with '&&' chaining and a certutil child process performing a URL download.


Response Playbook

Triage

  1. Confirm the host's Windows patch level against the MSRC advisory for CVE-2026-96951; determine whether the relevant October 2026 security update is installed.
  2. Reconstruct the full process tree for the alerting event: identify the injecting parent process, the spawned shell, and any grandchild processes, capturing full command lines and user context.
  3. Examine the injected command-line content to determine intent (reconnaissance, download, persistence) and whether metacharacters indicate successful injection versus benign chaining.
  4. Check whether the initiating service process (e.g., svchost, spoolsv, w3wp) is network-facing and had recent inbound connections correlating with the exploitation timestamp.

Containment

  1. Network-isolate the affected host via EDR to halt any attacker command-and-control or lateral movement.
  2. Suspend or kill the malicious process tree and disable the compromised service account pending investigation.
  3. Apply the vendor patch for CVE-2026-96951 or the MSRC-recommended workaround to all vulnerable hosts in the environment.

Evidence Collection

  1. Preserve process-creation logs (Sysmon EventID 1 / Security 4688), EDR process telemetry, and command-line history for the affected host.
  2. Capture memory and disk forensic images of the compromised host before remediation, and collect any files dropped by certutil/bitsadmin/curl downloads.

Escalation Criteria

  • ! Escalate to incident response if the injected commands achieved SYSTEM-level execution, downloaded second-stage payloads, or established persistence.
  • ! Escalate to threat-intel and leadership if multiple hosts show the same injection pattern, indicating active campaign exploitation of this KEV vulnerability.

Investigation Guide

Forensic Artifacts

  • > Sysmon EventID 1 / Security 4688 process-creation records showing anomalous parent-child lineage
  • > Command-line arguments containing shell metacharacters captured in EDR process telemetry
  • > Files written to disk by certutil, bitsadmin, or curl invoked through the injected command
  • > Windows Prefetch and ShimCache entries for shells spawned by service hosts

Tuning Guidance

Establish a baseline of legitimate service hosts that routinely spawn shells (deployment agents, backup tooling, IIS automation) and exclude those specific parent/command-line pairs. Tighten the recon/download keyword list to your environment's observed attacker tooling, and raise severity when the spawned shell writes executables or initiates outbound connections. Review exclusions after any patch deployment or application change.


Hunting Queries

Baselines shell interpreters spawned by non-interactive Windows service hosts carrying command-separator metacharacters, surfacing candidate command-injection attempts for review.

Hunting — KQL
kql
DeviceProcessEvents | where InitiatingProcessFileName in~ ("svchost.exe","spoolsv.exe","w3wp.exe","wsmprovhost.exe") | where FileName in~ ("cmd.exe","powershell.exe","pwsh.exe") | where ProcessCommandLine has_any ("&","|",";","`","$(") | project Timestamp, DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine
Hunting — SPL
spl
index=windows (EventCode=1 OR EventCode=4688) | eval parent=lower(coalesce(ParentImage,Creator_Process_Name)) | search (parent="*svchost.exe" OR parent="*spoolsv.exe" OR parent="*w3wp.exe") (CommandLine="*cmd.exe*" OR CommandLine="*powershell*") | regex CommandLine="[&|;`]|\$\(" | table _time host parent CommandLine

Atomic Red Team Tests

Test 1 Shell command chaining via metacharacter injection
windows

Simulates command injection by chaining a benign recon command onto a shell invocation using the & separator, mirroring exploitation telemetry of CVE-2026-96951.

Command

powershell
cmd.exe /c "echo input & whoami & net user"

Cleanup

powershell
echo No cleanup required; commands are read-only recon.

Expected Telemetry

Sysmon EventID 1 / Security 4688 showing cmd.exe with a command line containing '&' separators and whoami/net invocations.

Expected Detection

The kql/spl queries match on cmd.exe command line containing '&' metacharacter plus 'whoami' and 'net ' tooling.

Test 2 PowerShell encoded command via pipe injection
windows

Simulates injection of a base64-encoded PowerShell payload chained through a pipe, emulating download/execute behavior post-injection.

Command

powershell
powershell.exe -Command "echo input | powershell -enc ZQBjAGgAbwAgAHQAZQBzAHQA"

Cleanup

powershell
echo No cleanup required; payload only echoes text.

Expected Telemetry

Process-creation event for powershell.exe with command line containing '|' and '-enc' with a base64 blob.

Expected Detection

Queries match on powershell.exe command line containing '|' metacharacter and '-enc' tooling indicator.

Test 3 Service-host spawned download via certutil
windows

Simulates a follow-on download invoked through an injected command from a shell, using certutil to fetch a remote file as attackers commonly do after command injection.

Command

powershell
cmd.exe /c "ping 127.0.0.1 && certutil -urlcache -split -f http://127.0.0.1/test.txt %TEMP%\test.txt"

Cleanup

powershell
del /q %TEMP%\test.txt

Expected Telemetry

cmd.exe process with '&&' chaining and a certutil child process performing a URL download.

Expected Detection

Queries match on cmd.exe command line containing '&&' metacharacter and 'certutil' download tooling.

Related Detections