CVE Tools

CVE-2026-55120

Microsoft PowerPoint 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 which affected Microsoft products and versions you run (especially PowerPoint variants listed for Office/Office 365 and for Mac, plus PowerPoint 2016).
  2. Update Microsoft 365 apps / Microsoft Office using the official Office security updates page until you’re on the fixed release for CVE-2026-55120 (see https://aka.ms/OfficeSecurityReleases).
  3. For Microsoft Office 365 for Mac and Microsoft Office LTSC for Mac, upgrade to version 16.111.26071215 (includes both LTSC 2021 and LTSC 2024).
  4. For Microsoft PowerPoint 2016 (Windows), upgrade to 16.0.5561.1000.
  5. If you cannot update immediately, stop opening files from unknown/untrusted sources and have IT enforce safer attachment/file handling until patching is complete.

What it is

From the CVE record

Heap-based buffer overflow in Microsoft Office PowerPoint allows an unauthorized attacker to execute code locally.

In plain language

Written by AI from the record

CVE-2026-55120 is a Microsoft PowerPoint bug that can let an attacker run code on your computer when you open a crafted Office file; this is serious enough that most businesses should update even if you haven’t seen attacks.

Microsoft PowerPoint (part of Microsoft Office/Microsoft 365) has a memory-corruption flaw (CWE-122) that can be triggered by opening a specially crafted file, leading to remote code execution on the victim machine.

If you're affected

  • Full device compromise
  • Malware installation risk
  • Customer data theft
  • Business 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

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

  1. OpenVAS check added
  2. Patch availablepatch available, record updated, record updated, 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: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

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