# CVE-2025-60727: Microsoft 365 Apps Excel Out-of-Bounds Read Enables Remote Code Execution

> An out-of-bounds read vulnerability (CWE-125) in how Microsoft Excel parses crafted spreadsheet files allows an attacker to execute arbitrary code in the context of the current user when a victim opens a malicious Excel document. No authentication or elevated privileges are required, but user interaction is mandatory; the primary delivery vector is phishing with weaponized Excel attachments.

- **Published:** 2026-07-11T00:00:00Z
- **Last reviewed:** 2026-07-11T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-1205
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-excel-out-of-bounds-read-rce-tl-2026-1205.webp?v=1b066a98 (Threadlinqs threat intel: CVE-2025-60727 Microsoft Excel RCE: Detection & IOCs (TL-2026-1205) — High severity, 16 IOCs, 9 detection rules.)
- **ID:** TL-2026-1205
- **Severity:** HIGH (CVSS 7.8)
- **Category:** VULNERABILITY
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 16
- **CVEs:** CVE-2025-60727

## Description

CVE-2025-60727 is a locally-exploitable memory-safety vulnerability (CWE-125, out-of-bounds read) in Microsoft Excel's file-parsing engine, affecting Microsoft 365 Apps (Enterprise, x86/x64), Excel 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, and Office Online Server on Windows and macOS. The root cause is insufficient validation of length and offset values while Excel parses internal binary/OOXML spreadsheet structures (.xls/.xlsx). When Excel processes a specially crafted file, it reads memory beyond the bounds of an allocated buffer; an attacker who controls the malformed structure can leverage this out-of-bounds read to influence subsequent execution flow and ultimately achieve arbitrary code execution running with the current user's privileges (CIA impact: High/High/High).

Exploitation requires no authentication and no elevated privileges (PR:N), but does require user interaction (UI:R) — the victim must open the malicious file — which places this squarely in the phishing-delivered document category rather than a zero-click threat. Microsoft's CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base score 7.8) reflects a Local attack vector because exploitation occurs through local file parsing once the file is opened on the victim's machine, with Low attack complexity and no special conditions beyond the malformed file itself.

The likely attack chain: an adversary crafts a malicious .xls/.xlsx file with malformed internal structures (e.g., anomalous OLE objects, corrupted record length/offset fields), delivers it via a phishing email disguised as an invoice, business report, or shared document, or via file-sharing/drive-by download vectors, and waits for the victim to open it in Excel (desktop client, Microsoft 365 Apps, or Office Online Server rendering). Upon opening, the parsing logic reads past the allocated buffer, corrupting adjacent memory or leaking pointer/heap layout information that the attacker's crafted payload uses to redirect execution and run arbitrary code in the security context of the logged-on user — enabling follow-on activity such as dropper execution, persistence establishment, credential access, and lateral movement.

As of the source article date (2026-06-29) there is no public proof-of-concept exploit code and no confirmed in-the-wild/active exploitation; the CVE is not present in the CISA Known Exploited Vulnerabilities (KEV) catalog (checked against the 2026-07-10 KEV release, 1,637 entries). EPSS scoring is low (~0.05-0.49% depending on source/date), consistent with a vulnerability that is patched but not yet weaponized publicly. The vulnerability was first published by NVD/MSRC on 2025-11-11 and last updated 2026-06-17. Given the broad Microsoft 365/Office product footprint, the phishing-friendly delivery model, and historical precedent of Office memory-corruption bugs being weaponized after patch analysis (n-day exploitation via patch diffing), this threat remains a high-signal tracking candidate for detection engineering and patch-compliance monitoring despite the absence of confirmed active exploitation.

## MITRE ATT&CK

- T1598 Phishing for Information
- T1588 Obtain Capabilities
- T1587 Develop Capabilities
- T1566 Phishing
- T1204 User Execution
- T1203 Exploitation for Client Execution
- T1059 Command and Scripting Interpreter
- T1547 Boot or Logon Autostart Execution
- T1137 Office Application Startup
- T1068 Exploitation for Privilege Escalation
- T1685 Disable or Modify Tools
- T1140 Deobfuscate/Decode Files or Information
- T1036 Masquerading
- T1218 System Binary Proxy Execution
- T1003 OS Credential Dumping
- T1082 System Information Discovery
- T1083 File and Directory Discovery
- T1021 Remote Services
- T1005 Data from Local System
- T1071 Application Layer Protocol
- T1105 Ingress Tool Transfer
- T1041 Exfiltration Over C2 Channel
- T1565 Data Manipulation

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**EXCEL.EXE Spawning Command Shell or Scripting Interpreter (CVE-2025-60727 Post-Exploitation)** (`TL-2026-1205-SPL-002`)

Detects EXCEL.EXE spawning cmd.exe or powershell.exe as a child process, the core post-exploitation telemetry signature for CVE-2025-60727 once the out-of-bounds read has been leveraged to redirect execution flow. Excel legitimately never needs to launch a command interpreter.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1203, T1059.001, T1204.002
- **Data sources:** sysmon, windows_security, edr_process_telemetry
- **Severity:** critical
- **Confidence:** high

### Splunk SPL

```spl
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
| where match(ParentImage, "(?i)\\\\EXCEL\.EXE$") AND match(Image, "(?i)\\\\(cmd|powershell|powershell_ise)\.exe$")
| stats count min(_time) as first_seen values(CommandLine) as child_cmdline by host, user, ParentImage, Image, ParentProcessId, ProcessId
| convert ctime(first_seen)
| where count >= 1
```

### Microsoft KQL

```kql
DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ "EXCEL.EXE"
| where FileName in~ ("cmd.exe", "powershell.exe", "powershell_ise.exe")
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, InitiatingProcessId, ProcessId
| order by Timestamp desc
```

### Sigma

```yaml
title: Office Application Spawning Command Shell or PowerShell (CVE-2025-60727 pattern)
id: 8f2a1c6e-60727-4a11-9e60-tlintel0004
status: experimental
description: Detects EXCEL.EXE spawning cmd.exe or powershell.exe, consistent with post-exploitation code execution following an Office document-parsing memory-corruption vulnerability such as CVE-2025-60727.
references:
    - https://msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2025-60727
author: Threadlinqs Team
date: 2026-07-11
tags:
    - attack.execution
    - attack.t1059.001
    - attack.t1203
    - cve.2025.60727
logsource:
    category: process_creation
    product: windows
detection:
    selection_parent:
        ParentImage|endswith: '\\EXCEL.EXE'
    selection_child:
        Image|endswith:
            - '\\cmd.exe'
            - '\\powershell.exe'
            - '\\powershell_ise.exe'
    condition: selection_parent and selection_child
falsepositives:
    - Legitimate macro-driven automation that intentionally shells out (rare, should be an approved exception)
    - Third-party Excel add-ins that launch a helper process via cmd/powershell
level: high
```

**Known false positives:**

- Approved macro-driven business automation that intentionally shells out to cmd/powershell
- Third-party Excel add-ins launching helper processes via a command interpreter

**Tuning notes:** Maintain an allowlist of approved macro-automation command lines/hashes to suppress known-legitimate cases; alert at highest priority when the parent Excel process opened a file within the prior 5 minutes from an email attachment or download path.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Weaponized Excel Attachment Opened From Untrusted/Internet Zone (Mark-of-the-Web) Preceding Exploitation (locked: unlock with TL Creds)
- EXCEL.EXE Spawning LOLBAS Proxy-Execution Binaries (mshta.exe / rundll32.exe) (locked: unlock with TL Creds)
- Microsoft Defender ASR Rule Block/Audit — Office Child-Process Spawning Attempt (CVE-2025-60727) (locked: unlock with TL Creds)
- Excel Access-Violation Crash During Untrusted Spreadsheet Parsing (locked: unlock with TL Creds)
- Office Application Spawning Command Shell or Scripting Interpreter (CVE-2025-60727 pattern) (locked: unlock with TL Creds)
- Outbound Network Connection Initiated by Office Application Shortly After File Open (locked: unlock with TL Creds)
- Excel Access-Violation Crash During Untrusted Spreadsheet Parsing (CVE-2025-60727 Exploitation Attempt) (locked: unlock with TL Creds)
- Outbound Network Connection from EXCEL.EXE Shortly After Untrusted File Open (C2/Beacon) (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Microsoft 365 Apps RCE Vulnerability Exploited Using a Malicious Excel File](https://cybersecuritynews.com/microsoft-365-apps-rce-vulnerability-exploit/)
- [CVE-2025-60727 - Security Update Guide - Microsoft Excel Remote Code Execution Vulnerability](https://msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2025-60727)
- [CVE-2025-60727 Detail - NVD](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2025-60727)
- [CVE-2025-60727 - Tenable](https://www.tenable.com/cve/CVE-2025-60727)
- [CVE-2025-60727 - SentinelOne Vulnerability Database](https://www.sentinelone.com/vulnerability-database/cve-2025-60727/)
- [Microsoft 365 Apps RCE Vulnerability Lets Attackers Execute Code via Malicious Excel Files](https://gbhackers.com/microsoft-365-apps-rce-vulnerability/)
- [CISA Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-1205
