CVE Tools

CVE-2026-55045

Microsoft Office Remote Code Execution Vulnerability

No known exploitation. EPSS puts it in the 36th 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 which of these you run: Microsoft 365 Apps, Microsoft Office, Microsoft Office 365 for Mac, Microsoft Office LTSC for Mac 2021, Microsoft Office LTSC for Mac 2024, and Microsoft SharePoint Enterprise Server 2016/2019/Subscription Edition.
  2. Verify your installed version against the fixed versions below.
  3. Update Microsoft 365 Apps to the latest release from OfficeSecurityReleases.
  4. Update Microsoft Office to 16.0.5561.1000.
  5. Update Microsoft Office for Mac / LTSC for Mac (2021, 2024) to 16.111.26071215.
  6. Update SharePoint Enterprise Server 2016 to 16.0.5561.1001.
  7. Update SharePoint Server 2019 to 16.0.10417.20175.
  8. Update SharePoint Server Subscription Edition to 16.0.19725.20434.
  9. If you can’t update immediately, restrict access to the affected machines (especially limiting untrusted local access) until patches are applied.

What it is

From the CVE record

Out-of-bounds read in Microsoft Office allows an unauthorized attacker to execute code locally.

In plain language

Written by AI from the record

CVE-2026-55045 is a Microsoft Office security flaw that can let an attacker run code on your computer without needing a login or clicks, as long as a vulnerable Microsoft Office/SharePoint version is installed—so you should update soon.

CVE-2026-55045 is an out-of-bounds read in Microsoft Office that can be abused by an unauthorized local attacker to execute arbitrary code on the machine; the trigger requires a vulnerable Office installation (no user interaction or authentication).

If you're affected

  • Full device compromise
  • Malware installation
  • Operational disruption
  • Data theft risk

Exploitation

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

EPSS36th
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.4% chance of exploitation activity in the next 30 days, which ranks it in the 36th percentile of scored CVEs.

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

Lifecycle

9 events over 2 days, from the signal feeds we watch.

  1. OpenVAS check addedpatch available, record updated
  2. Record updated
  3. Publishedweakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

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

Scored 8.4 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 NoneNo user interaction needed — fully automated exploitation

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

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

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