CVE Tools

CVE-2026-64910

Microsoft Office Remote Code Execution Vulnerability

No known exploitation. EPSS puts it in the 38th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check every Office installation you use (Microsoft 365 Apps / Microsoft Office / Office 2019, 2021, 2024, plus any macOS versions of “Microsoft Office 365 for Mac” or “Microsoft Office LTSC for Mac 2021/2024”) and record the current version/build.
  2. For Microsoft Office 365 for Mac and both Microsoft Office LTSC for Mac 2021 and 2024, confirm you are on version 16.112.26081010 or later (fixed version).
  3. For Microsoft 365 Apps and Microsoft Office on Windows, update Office using Microsoft’s Office security release guidance for CVE-2026-64910 (see the Microsoft Office security releases link) and confirm the update completed.
  4. After updating, verify that the Office apps launch normally and that your next scheduled updates are enabled so you don’t fall behind again.

What it is

From the CVE record

Untrusted pointer dereference in Microsoft Office allows an unauthorized attacker to execute code locally.

In plain language

Written by AI from the record

CVE-2026-64910 is a Microsoft Office flaw that could let an attacker run code on your computer if you open a specially crafted Office file; you should update soon because this type of Office “open document” bug is one of the more common routes for real-world attacks.

CVE-2026-64910 is a Microsoft Office remote code execution vulnerability (CWE-822) that can be triggered when Office processes an untrusted, specially crafted document; Microsoft has released fixed builds for multiple Office products, including macOS versions 16.112.26081010.

If you're affected

  • Full device compromise
  • Ransomware staging
  • Data theft from Office files
  • Operational disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS38th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 38th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 3 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Record updatedrecord updated
  4. Publishedweakness classified, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store