Microsoft Outlook UI Does Not Warn User of Unsafe Action (CVE-2026-124194)
Detects host-based follow-on activity that may accompany exploitation of CVE-2026-124194, a spoofing vulnerability in Microsoft Office Outlook (CWE-356, product UI does not warn the user of unsafe actions). Per the NVD, an unauthorized attacker can perform spoofing over a network, and user interaction is required. The CVSS 3.1 base score is 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N). CVE-2026-124194 is listed in the CISA Known Exploited Vulnerabilities catalog, added 2026-11-10. As a detection aid, these rules surface Outlook spawning unusual child processes such as script interpreters or LOLBins, which can indicate malicious follow-on execution after a crafted message. These queries detect suspicious Outlook child-process behavior in general and are not a specific signature for this CVE.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Microsoft
- Product
- Office
Weakness (CWE)
Timeline
- Disclosed
- November 10, 2026
CVSS
- Attack Vector
- Network
- Attack Complexity
- Low
- Privileges Required
- None
- User Interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
What is CVE-2026-124194 Microsoft Outlook UI Does Not Warn User of Unsafe Action (CVE-2026-124194)?
Microsoft Outlook UI Does Not Warn User of Unsafe Action (CVE-2026-124194) (CVE-2026-124194) 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 Outlook UI Does Not Warn User of Unsafe Action (CVE-2026-124194), covering the data sources and telemetry it touches: Microsoft Defender for Endpoint. 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
// df00tech DF00-c8c119cf3b · https://df00tech.com/detections/CVE-2026-124194 · licence: https://df00tech.com/detections/licence
let outlook = dynamic(["outlook.exe"]);
let suspiciousChildren = dynamic(["powershell.exe","cmd.exe","wscript.exe","cscript.exe","mshta.exe","rundll32.exe","regsvr32.exe","certutil.exe","curl.exe","bitsadmin.exe"]);
DeviceProcessEvents
| where InitiatingProcessFileName in~ (outlook)
| where FileName in~ (suspiciousChildren)
| project Timestamp, DeviceId, DeviceName, AccountName, InitiatingProcessFileName, FileName, ProcessCommandLine, InitiatingProcessCommandLine
| order by Timestamp desc Outlook spawning script interpreters or LOLBins, a signal of suspicious follow-on execution after a crafted message.
Data Sources
Required Tables
False Positives
- Legitimate Outlook add-ins or COM automation that launch helper processes
- Enterprise mail-handling scripts invoked by approved VBA macros
- Admin troubleshooting that launches cmd/powershell from an Office context
Query fingerprint DF00-c8c119cf3b · licence
Sigma logsource & community rules
The detection logic for Microsoft Outlook UI Does Not Warn User of Unsafe Action (CVE-2026-124194) (CVE-2026-124194) 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:
Platform-specific guides for CVE-2026-124194
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 further down this page.
- Test 1 Outlook spawns PowerShell (simulated child process)
Expected signal: Process creation event with parent image outlook.exe and child powershell.exe
- Test 2 Outlook spawns mshta fetching remote content
Expected signal: Process creation of mshta.exe with parent outlook.exe and outbound connection attempt
- Test 3 Outlook spawns rundll32 LOLBin
Expected signal: Process creation of rundll32.exe with parent outlook.exe
Response Playbook
Triage
- Confirm the alerting host runs a Microsoft Office/Outlook build affected by CVE-2026-124194 and whether the November 2026 security update has been applied.
- Identify the parent Outlook process and the exact child command line, and determine whether it correlates with a recently received, opened, or previewed email.
- Review the mailbox for the triggering message: sender, embedded links or objects, and the user action that preceded the child process.
- Check whether the spawned process made outbound network connections or wrote files to disk.
Containment
- Isolate the affected endpoint from the network to prevent follow-on command execution or data exfiltration.
- Quarantine the triggering email across the organization (purge from mailboxes) and block the sender and associated infrastructure.
- Disable or block the abused child binary via application control if the activity is confirmed malicious.
Evidence Collection
- Preserve the original email (headers and raw .eml/.msg) and any embedded objects or linked content.
- Collect process-creation telemetry (Sysmon EID 1 / EDR), command lines, and parent-child lineage from OUTLOOK.EXE.
- Capture network connection logs and any files created by the spawned process for malware analysis.
Escalation Criteria
- ! Escalate to incident response if the spawned process executed remote payloads or established C2 connectivity.
- ! Escalate if credential-theft or lateral-movement indicators follow the Outlook-triggered activity.
- ! Escalate if multiple mailboxes received the same crafted message, indicating a campaign.
Investigation Guide
Forensic Artifacts
- >
Original .msg/.eml message with headers and embedded objects - >
OUTLOOK.EXE child-process creation events and command lines - >
Outlook temp/cache artifacts and any files written by the spawned process - >
Outbound network connection records correlated with mail receipt time
Tuning Guidance
Build an allowlist of known-good Outlook add-ins and COM automation that legitimately launch helper processes in your environment, then exclude those parent-child-command-line combinations. Focus alerting on interpreters and LOLBins (powershell, mshta, rundll32, certutil) rather than common signed Office helpers, and raise severity when the child process makes outbound network connections shortly after mail receipt.
Hunting Queries
Baseline and hunt for all child processes of Outlook across the fleet to surface rare or anomalous launches.
// df00tech DF00-c8c119cf3b · https://df00tech.com/detections/CVE-2026-124194 · licence: https://df00tech.com/detections/licence
DeviceProcessEvents | where InitiatingProcessFileName =~ "outlook.exe" | summarize count() by FileName, ProcessCommandLine, DeviceName | order by count_ desc ``` df00tech DF00-c8c119cf3b · https://df00tech.com/detections/CVE-2026-124194 · licence: https://df00tech.com/detections/licence ```
index=endpoint parent_process_name="outlook.exe" | stats count by process_name, CommandLine, host | sort -count Atomic Red Team Tests
Simulates Outlook spawning a child process by renaming a shell to emulate the parent lineage in a lab.
Command
copy C:\Windows\System32\cmd.exe %TEMP%\outlook.exe & %TEMP%\outlook.exe /c powershell.exe -NoProfile -Command "Write-Host CVE-2026-124194-test" Cleanup
del %TEMP%\outlook.exe Expected Telemetry
Process creation event with parent image outlook.exe and child powershell.exe
Expected Detection
KQL/SPL/EQL rules fire on outlook.exe parent spawning powershell.exe
Simulates a child process launching mshta to retrieve remote script content from a lab host.
Command
copy C:\Windows\System32\cmd.exe %TEMP%\outlook.exe & %TEMP%\outlook.exe /c mshta.exe http://127.0.0.1:8000/test.hta Cleanup
del %TEMP%\outlook.exe Expected Telemetry
Process creation of mshta.exe with parent outlook.exe and outbound connection attempt
Expected Detection
Rules match mshta.exe child of outlook.exe
Simulates Outlook invoking rundll32 in a lab environment.
Command
copy C:\Windows\System32\cmd.exe %TEMP%\outlook.exe & %TEMP%\outlook.exe /c rundll32.exe shell32.dll,Control_RunDLL Cleanup
del %TEMP%\outlook.exe Expected Telemetry
Process creation of rundll32.exe with parent outlook.exe
Expected Detection
Rules match rundll32.exe child of outlook.exe
Related Detections
Tactic Hubs
Related Techniques
Same Tactic: Initial Access
Browse by tactic
- Reconnaissance TA0043
- Resource Development TA0042
- Initial Access TA0001
- Execution TA0002
- Persistence TA0003
- Privilege Escalation TA0004
- Stealth TA0005
- Defense Impairment TA0112
- Credential Access TA0006
- Discovery TA0007
- Lateral Movement TA0008
- Collection TA0009
- Command and Control TA0011
- Exfiltration TA0010
- Impact TA0040