Skip to navigation

Threat reportVulnerabilityTL-2026-0209

Microsoft Office Preview Pane Remote Code Execution — CVE-2026-26110 (Type Confusion) & CVE-2026-26113 (Untrusted Pointer Dereference)

criticalPATCHED

Two critical remote code execution vulnerabilities in Microsoft Office (CVE-2026-26110, CVE-2026-26113) exploitable via the Outlook Preview Pane without user interaction. CVE-2026-26110 is a type confusion flaw and CVE-2026-26113 is an untrusted pointer dereference, both allowing unauthenticated attackers to execute arbitrary code by sending a crafted Office document that triggers on preview.

Key facts

IdentifiersTL-2026-0209, CVE-2026-26110, CVE-2026-26113
SeverityCRITICAL
CVSS8.4 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N)
EPSSCVE-2026-26113: 0.4% (35.0th percentile); CVE-2026-26110: 0.3% (26.5th percentile)
Affected productsMicrosoft Microsoft Office 2016; Microsoft Microsoft Office 2019; Microsoft Microsoft Office LTSC 2021; Microsoft Microsoft Office LTSC 2024; Microsoft Microsoft 365 Apps for Enterprise
Weaknesses (CWE)CWE-843, CWE-822
ToolsSnort SIDs 66089-66092, 66096-66097, 66101-66104 (Snort 2); 301442-301446 (Snort 3)
MITRE ATT&CK techniquesT1003 OS Credential Dumping, T1005 Data from Local System, T1027 Obfuscated Files or Information, T1036 Masquerading, T1041 Exfiltration Over C2 Channel, T1055 Process Injection, T1057 Process Discovery, T1059 Command and Scripting Interpreter, T1068 Exploitation for Privilege Escalation, T1071 Application Layer Protocol, T1082 System Information Discovery, T1203 Exploitation for Client Execution and 4 more in the attack flow
MotivationUNKNOWN
Target sectorsgovernment, financial, healthcare, education, technology, defense, energy, manufacturing, legal, media
Target regionsGlobal
Detection rules9 (1 shown free)
Sources14 cited sources

Detection coverage

As of 2026-03-11, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0209 across Splunk SPL, Microsoft KQL and Sigma, covering 15 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Office Preview Pane Exploitation — Suspicious Child Process Spawning via Sysmon

Detects Microsoft Office applications (Outlook, Word, Excel, PowerPoint) spawning suspicious child processes such as command shells, script interpreters, or living-off-the-land binaries via Sysmon process creation events. This indicates potential exploitation of CVE-2026-26110 (type confusion) or CVE-2026-26113 (untrusted pointer dereference) through the Preview Pane rendering engine.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1203, T1566.001, T1059
  • Data sources: sysmon, windows_security
  • Severity: critical
  • Confidence: high

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 ParentImage IN ("*\\OUTLOOK.EXE", "*\\WINWORD.EXE", "*\\EXCEL.EXE", "*\\POWERPNT.EXE") Image IN ("*\\cmd.exe", "*\\powershell.exe", "*\\pwsh.exe", "*\\wscript.exe", "*\\cscript.exe", "*\\mshta.exe", "*\\rundll32.exe", "*\\regsvr32.exe") | eval risk_score=case(match(Image, "(?i)powershell"), 90, match(Image, "(?i)mshta"), 85, match(Image, "(?i)rundll32"), 80, 1=1, 70) | table _time, ComputerName, User, ParentImage, Image, CommandLine, ParentCommandLine, ProcessId, risk_score | sort -_time

Microsoft KQL

DeviceProcessEvents | where Timestamp > ago(24h) | where InitiatingProcessFileName in~ ("OUTLOOK.EXE", "WINWORD.EXE", "EXCEL.EXE", "POWERPNT.EXE") | where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe") | extend RiskScore = case(FileName =~ "powershell.exe", 90, FileName =~ "mshta.exe", 85, FileName =~ "rundll32.exe", 80, 70) | project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, ProcessId, RiskScore | sort by Timestamp desc

Sigma

title: Office Application Spawning Suspicious Child Process — CVE-2026-26110/26113 Exploitation
id: 66f8088a-821d-4fd8-8334-ac31889d842c
status: experimental
description: Detects Microsoft Office applications spawning suspicious child processes indicating potential Preview Pane RCE exploitation via CVE-2026-26110 or CVE-2026-26113.
references:
    - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26110
    - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26113
author: Threadlinqs Team
date: 2026/03/11
tags:
    - attack.execution
    - attack.t1203
    - attack.initial_access
    - attack.t1566.001
    - cve.2026.26110
    - cve.2026.26113
logsource:
    product: windows
    category: process_creation
detection:
    selection_parent:
        ParentImage|endswith:
            - '\OUTLOOK.EXE'
            - '\WINWORD.EXE'
            - '\EXCEL.EXE'
            - '\POWERPNT.EXE'
    selection_child:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
            - '\pwsh.exe'
            - '\wscript.exe'
            - '\cscript.exe'
            - '\mshta.exe'
            - '\rundll32.exe'
            - '\regsvr32.exe'
    condition: selection_parent and selection_child
falsepositives:
    - Legitimate Office add-ins or macros spawning command shells
    - IT automation scripts triggered via Office COM interfaces
level: critical

Known false positives:

  • Legitimate Office add-ins or macros that spawn command shells for automation
  • IT management scripts triggered via Office COM add-in interfaces

Tuning notes: Exclude known legitimate Office add-ins by adding ParentCommandLine filters. Whitelist specific IT automation tools that spawn shells from Office processes. Adjust risk_score thresholds based on environment baseline.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Office Preview Pane Exploitation — MDE Process Chain Detection · unlock with TL Creds
  • Post-Exploitation DLL Sideloading — Unsigned Library Loaded from Temp by Office Process · unlock with TL Creds
  • C2 Preparation — System Discovery Commands from Office-Spawned Process Tree · unlock with TL Creds
  • Office Preview Pane Exploitation — WER Crash with Access Violation During Document Rendering · unlock with TL Creds
  • Post-Exploitation Blocked — ASR Rule Prevented Office Child Process Creation · unlock with TL Creds
  • C2 Persistence — Scheduled Task Creation by Office-Spawned Process · unlock with TL Creds
  • Post-Exploitation Registry Persistence — Run Key Modified with Suspicious LOLBin Reference · unlock with TL Creds
  • C2 Communication — Outbound Connections from Office-Spawned Process Tree · unlock with TL Creds

Indicators of compromise

As of 2026-03-11, Threadlinqs Intelligence tracks 15 indicators of compromise for TL-2026-0209.

15 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Microsoft's March 2026 Patch Tuesday addressed two critical remote code execution vulnerabilities in Microsoft Office that share the Preview Pane as a common attack vector, creating a near zero-click exploitation scenario.

CVE-2026-26110 is a type confusion vulnerability (CWE-843) in Microsoft Office caused by improper handling of incompatible data types during resource access. When a specially crafted Office document is rendered in the Preview Pane, the application incorrectly interprets a data structure as a different type, leading to memory corruption and arbitrary code execution with the privileges of the logged-in user.

CVE-2026-26113 is an untrusted pointer dereference vulnerability (CWE-822) in Microsoft Office where the application improperly handles memory pointers during document rendering. An attacker can craft a malicious Office document that manipulates how the application accesses memory, allowing arbitrary pointer dereference and subsequent code execution.

Both vulnerabilities share critical characteristics: low attack complexity, no privileges required, no user interaction needed, and the Preview Pane as an attack vector. The exploitation chain begins when a victim receives a malicious Office document — typically via email — and the Outlook Preview Pane automatically renders it. The rendering process triggers either the type confusion or pointer dereference flaw, granting the attacker code execution on the target system.

Although Microsoft classifies these as remote code execution vulnerabilities, the CVSS attack vector is Local (AV:L) because the exploit code ultimately executes on the local device. The remote delivery mechanism (email) serves as the initial access vector, while exploitation occurs during local document parsing.

Microsoft assessed exploitation as 'Less Likely' at the time of release, and neither vulnerability was publicly disclosed or observed in active attacks. However, the Preview Pane attack surface has historically been a high-value target for threat actors, and security researchers at the Zero Day Initiative noted these follow a recurring pattern of Office Preview Pane vulnerabilities that are 'just a matter of time' before appearing in active exploits.

Cisco Talos released Snort rules (IDs 66089-66092, 66096, 66097, 66101-66104 for Snort 2; 301442-301446 for Snort 3) to detect exploitation attempts. Affected products include Microsoft Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, and Microsoft 365 Apps for Enterprise.

The critical risk factor is the near zero-click nature of the attack: organizations with the Outlook Preview Pane enabled (the default configuration) are vulnerable to exploitation without any user action beyond receiving a malicious email. This makes these vulnerabilities particularly dangerous for enterprise environments where Office is universally deployed.

---

**Revalidated on 2026-03-12**

REVALIDATION NOTE (2026-03-12): Core description remains accurate and comprehensive. Two clarifications warranted: (1) CVSS Score Variance — The advisory uses CVSS 8.4 consistent with MSRC's assessment. Some third-party sources report 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H per some analyses) or even 9.8. The discrepancy stems from how the attack vector is scored — MSRC uses AV:L because exploitation executes locally during document parsing, while some analysts use AV:N because the delivery mechanism is network-based (email). The AV:L/8.4 score used in the advisory follows MSRC's authoritative assessment and is technically correct for the exploitation step itself. (2) Zero-Day Clarification — CyberScoop confirms this March Patch Tuesday is the first in six months with NO actively exploited zero-days. The two publicly disclosed zero-days are CVE-2026-21262 (SQL Server privilege escalation) and CVE-2026-26127 (.NET DoS) — NOT CVE-2026-26110/26113. This further validates the 'THEORETICAL' exploitability rating and 'exploitation-less-likely' tag. (3) Help Net Security reports six CVEs flagged as 'more likely' to be exploited, all involving privilege escalation — CVE-2026-26110 and CVE-2026-26113 are explicitly NOT among them.

MITRE ATT&CK techniques by tactic:

credential-access

T1003 OS Credential Dumping

collection

T1005 Data from Local System

defense-evasion

T1027 Obfuscated Files or Information; T1036 Masquerading; T1055 Process Injection

exfiltration

T1041 Exfiltration Over C2 Channel

discovery

T1057 Process Discovery; T1082 System Information Discovery

execution

T1059 Command and Scripting Interpreter; T1203 Exploitation for Client Execution; T1204 User Execution

privilege-escalation

T1068 Exploitation for Privilege Escalation

command-and-control

T1071 Application Layer Protocol

persistence

T1547 Boot or Logon Autostart Execution

impact

T1565 Data Manipulation

initial-access

T1566 Phishing

Remediation

Patches

  • Microsoft March 2026 Patch Tuesday — Security Update for Microsoft Office (CVE-2026-26110)
  • Microsoft March 2026 Patch Tuesday — Security Update for Microsoft Office (CVE-2026-26113)
  • Apply updates via Windows Update, Microsoft Update Catalog, WSUS, or Configuration Manager

Immediate actions

  • Apply March 2026 Patch Tuesday security updates for all Microsoft Office installations immediately
  • Disable the Outlook Preview Pane across the organization via Group Policy (Outlook > Reading Pane > Off)
  • Disable Windows Explorer Preview Pane for Office file types
  • Block Office file attachments from untrusted external senders at the email gateway
  • Enable Attack Surface Reduction (ASR) rules for Office applications

Workarounds

  • Disable Outlook Preview Pane: View > Reading Pane > Off
  • Disable Windows Explorer Preview Pane for Office documents
  • Restrict opening Office files from untrusted sources
  • Configure Office to open documents in Protected View by default

Longer-term hardening

  • Deploy EDR with behavioral detection for anomalous Office process activity
  • Implement application whitelisting to prevent unauthorized child process spawning from Office applications
  • Configure Microsoft Defender Application Guard for Office to isolate untrusted documents
  • Establish automated patch management for Office products with SLA of 48 hours for critical vulnerabilities
  • Enable Protected View for all Office documents from external sources

Affected and fixed versions

  • Microsoft — Microsoft Office 2016
    Vulnerable versions: All builds prior to March 2026 patch
    Fixed in: March 2026 Security Update
  • Microsoft — Microsoft Office 2019
    Vulnerable versions: All builds prior to March 2026 patch
    Fixed in: March 2026 Security Update
  • Microsoft — Microsoft Office LTSC 2021
    Vulnerable versions: All builds prior to March 2026 patch
    Fixed in: March 2026 Security Update
  • Microsoft — Microsoft Office LTSC 2024
    Vulnerable versions: All builds prior to March 2026 patch
    Fixed in: March 2026 Security Update
  • Microsoft — Microsoft 365 Apps for Enterprise
    Vulnerable versions: All builds prior to March 2026 patch
    Fixed in: March 2026 Security Update

Timeline

  • Microsoft assesses exploitation as Less Likely; no public disclosure or active exploitation observed at time of release. ZDI warns Preview Pane vulnerabilities historically progress to active exploitation
  • Cisco Talos releases Snort detection rules (IDs 66089-66092, 66096, 66097, 66101-66104 for Snort 2; 301442-301446 for Snort 3) covering exploitation attempts
  • CrowdStrike, Zero Day Initiative, Cisco Talos, Tenable, and Qualys publish detailed Patch Tuesday analysis identifying Preview Pane as attack vector for both CVEs
  • Microsoft Security Response Center publishes advisories for CVE-2026-26110 (type confusion) and CVE-2026-26113 (untrusted pointer dereference) rated Critical with CVSS 8.4
  • Microsoft releases March 2026 Patch Tuesday security updates fixing CVE-2026-26110 and CVE-2026-26113 among 79+ other vulnerabilities
  • CyberScoop reports March 2026 Patch Tuesday is the first in six months with no actively exploited zero-days, confirming theoretical-only exploitation status for CVE-2026-26110 and CVE-2026-26113
  • Multiple security vendors (Dark Reading, SecurityWeek, Help Net Security, Dataconomy) publish independent analyses confirming CVE-2026-26110 and CVE-2026-26113 as critical Office Preview Pane RCE vulnerabilities with no observed active exploitation
  • Threadlinqs Intelligence Platform publishes TL-2026-0209 threat advisory with full MITRE ATT&CK mapping, detection coverage, and remediation guidance
  • Threadlinqs Intelligence revalidation: all core claims verified against 14+ independent sources. No public PoC, no CISA KEV listing, no confirmed active exploitation. CVSS score variance noted (8.4 MSRC vs. 8.8/9.8 in some third-party reports).
  • As of 2026-05-29, CVE-2026-26110/26113 (Office Preview Pane RCE) remain fully patched via Microsoft's March 2026 update with no active exploitation, no public PoC, and no CISA KEV listing (confirmed against NVD and the May 20/27 KEV additions). Microsoft rated exploitation "Less Likely"; PATCHED status is unchanged and no successor threat exists.

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 14 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats