Skip to main content
Mallory
HighVulnerability

CVE-2026-118707: Heap-based buffer overflow remote code execution in Microsoft Excel

Published Nov 10, 2026 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days12 mentions · peak 9 in a dayToday
CVSS8.8High · v3.1
EPSS0.93%61st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-118707CWE-122 · Heap-based Buffer Overflow

CVE-2026-118707 is a heap-based buffer overflow in Microsoft Excel that allows an unauthenticated attacker to achieve remote code execution by persuading a user to open a specially crafted workbook and interact with affected workbook features. Affected products include Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024 on Windows, Office 365 and Office LTSC on Mac, and Office Online Server. The responsible function, workbook record type, and precise affected feature have not been publicly identified. The Preview Pane is not an attack vector. Microsoft released fixes on November 10, 2026, rates the vulnerability Important, and assigns a CVSS v3.1 base score of 8.8.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits attacker-controlled code execution, potentially compromising the confidentiality, integrity, and availability of the affected system and resources accessible to the compromised process. The vulnerability does not establish independent elevation to administrator privileges. Microsoft reported no exploitation or public disclosure at initial publication and assessed exploitation as less likely.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific workaround or configuration-based mitigation is documented. Until patched, avoid opening untrusted or unexpected Excel workbooks. Preview Pane exposure alone does not trigger this vulnerability; this limitation is not a substitute for installing the update.

Remediation

Patch, then assume compromise.

Install the applicable November 10, 2026 Microsoft security update and verify the installed build for the product and servicing channel. Fixed Windows Office LTSC builds are 16.0.14334.21048 for LTSC 2021 and 16.0.17932.21140 for LTSC 2024. The fixed Mac build is 16.115.26110837 for Office 365, Office LTSC 2021, and Office LTSC 2024. Microsoft 365 Apps for Enterprise fixes are: Current Channel version 2610 build 20527.20196; Monthly Enterprise Channel version 2610 build 20527.20194, version 2609 build 20430.20264, or version 2608 build 20326.20320; Semi-Annual Enterprise Channel version 2610 build 20527.20192, version 2609 build 20430.20262, or version 2608 build 20326.20318. Use the update applicable to the installed branch. Windows client updates are delivered through Click-to-Run, and Mac updates through Microsoft AutoUpdate or administrator-deployed packages. For Office Online Server, install KB5002946, which supplies build 16.0.10417.20236 and supersedes KB5002928. The server update requires the release version of Office Online Server and is available through Microsoft Update, Microsoft Update Catalog, and Microsoft Download Center.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft Corporation365 Appsapplication
Microsoft CorporationMicrosoft 365application
Microsoft CorporationOffice 2021application
Microsoft CorporationOffice 2024application
Microsoft CorporationOffice 365application
Microsoft CorporationOffice Macos 2021application
Microsoft CorporationOffice Macos 2024application
Microsoft CorporationOffice Online Serverapplication
FAQ

Frequently asked questions

Is CVE-2026-118707 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-118707 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-118707?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-118707.
Is there a patch for CVE-2026-118707?
Install the applicable November 10, 2026 Microsoft security update and verify the installed build for the product and servicing channel. Fixed Windows Office LTSC builds are 16.0.14334.21048 for LTSC 2021 and 16.0.17932.21140 for LTSC 2024.
What products are affected by CVE-2026-118707?
Microsoft Corporation 365 Apps, Microsoft Corporation Microsoft 365, Microsoft Corporation Office 365, Microsoft Corporation Office Online Server, Microsoft Corporation Office 2021, and 3 more.
How severe is CVE-2026-118707?
CVE-2026-118707 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.93% (61st percentile) as of Nov 16, 2026.
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.