Skip to main content

Microsoft Excel CVE-2026-97761

| EUVDEUVD-2026-99820 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-10-13 secure@microsoft.com GHSA-7h6f-wph8-848j
8.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver crafted Excel file via phishing
  2. Delivery
    Victim opens malicious spreadsheet
  3. Exploit
    Trigger stack-based buffer overflow in parser
  4. Execution
    Execute arbitrary code as user
  5. Impact
    Compromise host and data

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a user to open a maliciously crafted Excel document (UI:R in the CVSS vector) - the flaw is not reachable without victim interaction, which is the primary limiting factor. No authentication or elevated privileges are needed (PR:N), and no special server-side configuration is required; the vulnerable code path is the standard Excel file-parsing routine present in default installations. Affected products per EUVD include Microsoft Office LTSC 2024 (before 16.0.17932.21056), Microsoft 365 Apps for Enterprise, Office 365 for Mac, and Office LTSC for Mac 2021/2024, so both Windows and macOS Office builds are in scope. The attack vector is 'network' in the sense that the malicious file is delivered remotely (email/web), but code execution occurs locally when the file is opened, running in the context of the current user rather than as SYSTEM/root.

Impact

This is a genuine high-priority client-side vulnerability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a network-deliverable, low-complexity, unauthenticated code-execution flaw whose only gating factor is user interaction (UI:R) - i.e., a victim must open a crafted Excel document. This is the archetypal phishing/malicious-attachment attack surface, which attackers routinely weaponize. However, several threat-intel signals that would confirm imminent mass exploitation are ABSENT from the input: no EPSS exploitation-probability score is provided, the CVE is NOT listed in CISA KEV, and no public POC is indicated. Therefore, per the precision rules, exploitation status is 'no public exploit identified at time of analysis' - this is high real-world risk by nature of the product and vector, but there is no evidence of active exploitation at this time. The signals are internally consistent (no conflict between CVSS and description; both indicate remote, user-interaction-gated RCE), so the main caveat is simply that dynamic exploitation metrics (EPSS/KEV/POC) are unavailable to refine urgency. A patch is confirmed available from the vendor, so remediation is actionable now.

Exploit ScenarioDerived

An attacker crafts a malicious Excel spreadsheet that triggers a stack-based buffer overflow (CWE-121) in Microsoft Office Excel's file parsing and delivers it via phishing email or a download link. When the targeted user opens the file, the overflow corrupts the stack and executes attacker-controlled code in the context of the user. No public exploit code is identified at time of analysis, but the AV:N/AC:L/UI:R profile makes this a practical, low-effort phishing payload.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Stack-based buffer overflow in the Excel document parser allows a remote, unauthenticated attacker to execute code in the context of the current user when a victim opens a maliciously crafted spreadsheet. Exploitation requires user interaction (UI:R) - the file must be opened - and the attacker gains no elevated privileges, with code running locally rather than as SYSTEM or root, though impact to confidentiality, integrity and availability is rated high for that user context. The flaw affects Microsoft Office LTSC 2024 before 16.0.17932.21056, Microsoft 365 Apps for Enterprise, Microsoft Office 365 for Mac, and Office LTSC for Mac 2021/2024, and a vendor patch is available; no public exploit code was identified at time of analysis and exploitation has not been confirmed as active (no CISA KEV listing), so risk is driven by the large Office install base and the ease of delivering a file by email or web rather than by observed attacks.

RemediationAI

Apply the Microsoft update, which is available from the vendor: Office LTSC 2024 on Windows must be updated to build 16.0.17932.21056 or later, while Microsoft 365 Apps for Enterprise, Office 365 for Mac, and Office LTSC for Mac 2021/2024 are serviced through Microsoft's Office security release channel (verify the currently offered build via https://aka.ms/OfficeSecurityReleases and the per-product mapping in https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-97761). For Click-to-Run installations, ensure automatic updates are enabled and force an update check so clients pick up the fixed build; for MSI/volume-licensed and Mac deployments, push the corresponding patch through your software distribution tooling, and confirm the version actually changed because Office update failures are silent in many configurations. Until patching is complete, the most effective compensating control is attack-surface reduction around file delivery and opening: enforce Protected View for files originating from the internet and for attachments (trade-off: additional prompt friction and possible breakage of trusted automation flows), use Trust Center file-block settings to disable opening of legacy Excel binary formats such as XLS/BIFF if they are not business-critical (trade-off: users lose access to old workbooks, which may need a conversion exception process), and detonate or sandbox inbound Office attachments at the mail/web gateway (trade-off: latency and potential false positives on complex legitimate spreadsheets). Since exploitation requires the user to open the file (UI:R) and runs with the user's privileges rather than as SYSTEM, restricting use of administrative accounts for day-to-day email and browsing meaningfully limits the blast radius; endpoint detection tuned to Excel spawning child processes (for example script interpreters or command shells) provides a useful detection backstop for this class of bug.

Affected VersionsENISA

Microsoft Office LTSC 2024 16.0.0 <16.0.17932.21056
Microsoft 365 Apps for Enterprise 16.0.1 <https://aka.ms/OfficeSecurityReleases
Microsoft Office 365 for Mac 1.0.0 <publication
Microsoft Office LTSC for Mac 2024 16.0.0 <publication
Microsoft Office LTSC for Mac 2021 16.0.1 <publication

Affected Packages

euvd microsoft_office_ltsc_2024 fix: 16.0.17932.21056

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-121, a stack-based buffer overflow, occurring in the code path Excel uses to parse spreadsheet content - the same in-process parsing routine exercised whenever a workbook is loaded on a default installation, with no special server configuration required. Because the vulnerable buffer is allocated on the stack, a crafted value that exceeds its expected size can overwrite adjacent stack memory, including saved control data, which is the classic route from memory corruption to arbitrary code execution within the Excel process (and therefore under the user's token). The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H indicates the file is delivered over a network (mail, web download, chat) and no credentials or privileges are needed, with the sole gating condition being that the victim opens the document; the scope remains unchanged, meaning exploitation is contained to the Excel process context rather than crossing a security boundary such as the OS or kernel. Per the ENISA EUVD data, affected binaries span both Windows and macOS Office builds, and the CPE/advisory coverage confirms this is a shared cross-platform parsing component rather than a single-platform defect, which matters for organizations that assume Mac Office is out of scope.

Know when 365 Apps gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Malicious file delivered remotely (AV:N) and opened without special skill (AC:L) by any user (PR:N) but requiring their action (UI:R), yielding user-context RCE with full CIA impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:22 cve.org
HIGH 8.8

DescriptionCVE.org

Stack-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

Microsoft Excel users across Windows and Mac-including Office LTSC 2024, Microsoft 365 Apps for Enterprise, and Office 365 for Mac-are affected by a high-severity code execution flaw that can be triggered when a user opens a malicious spreadsheet. Since no public exploit identified at time of analysis, the immediate risk is driven by the broad Office install base and the ease of delivering a file by email or web rather than by observed attacks. Leadership should prioritize patching to protect user-context data and maintain productivity.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.8%
Top 44% exploitable
Prevalence
Ubiquitous
Microsoft Excel is deployed across nearly all enterprise and consumer environments
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.8%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

CVE-2024-21413 CRITICAL POC
9.8 Feb 13

Microsoft Outlook Remote Code Execution Vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is remotel

CVE-2021-42292 HIGH
7.8 Nov 10

Microsoft Excel Security Feature Bypass Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authenti

CVE-2023-35311 HIGH
8.8 Jul 11

Microsoft Outlook Security Feature Bypass Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely

CVE-2023-21715 HIGH
7.3 Feb 14

Microsoft Publisher Security Feature Bypass Vulnerability. Rated high severity (CVSS 7.3), this vulnerability is low att

CVE-2026-21509 HIGH POC
7.8 Jan 26

Microsoft Office contains a security feature bypass (CVE-2026-21509, CVSS 7.8) where reliance on untrusted inputs in sec

CVE-2026-21514 HIGH
7.8 Feb 10

Microsoft Office Word contains a security decision bypass (CVE-2026-21514, CVSS 7.8) through reliance on untrusted input

CVE-2021-38646 HIGH
7.8 Sep 15

Microsoft Office Access Connectivity Engine Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vu

CVE-2021-34478 HIGH
7.8 Aug 12

Microsoft Office Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentic

CVE-2021-34501 HIGH
7.8 Jul 14

Microsoft Excel Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no authentica

CVE-2025-47957 HIGH POC
8.4 Jun 10

Use-after-free vulnerability in Microsoft Office Word that allows local, unauthenticated attackers to execute arbitrary

CVE-2022-41106 HIGH
8.8 Nov 09

Microsoft Excel Remote Code Execution Vulnerability. Rated high severity (CVSS 8.8), this vulnerability is remotely expl

CVE-2023-33148 HIGH POC
7.8 Jul 11

Microsoft Office Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is low attack

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy