CVE Tools

CVE-2026-55043

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 Microsoft Office/PowerPoint products and versions you use (including Microsoft 365 apps, Office 2019/2021/2024, and any Mac variants like Office 365 for Mac or Office LTSC for Mac).
  2. Update Microsoft Office/PowerPoint using Microsoft’s Office security updates page referenced by the CVE: https://aka.ms/OfficeSecurityReleases (Windows and applicable Microsoft Office channels).
  3. On Mac, update PowerPoint/Office to 16.111.26071215 (covers Microsoft Office 365 for Mac, Office LTSC for Mac 2021, and Office LTSC for Mac 2024).
  4. After updating, verify in PowerPoint “About” that the installed version matches the fixed version for your edition (or that you’re on the patched build via the Office security update release).

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-55043 is a Microsoft PowerPoint security bug that could let someone run code after convincing a user to open a specially made PowerPoint file; if you run Microsoft Office/PowerPoint, you should patch promptly.

CVE-2026-55043 is a PowerPoint remote code execution issue (CWE-122/CWE-190) caused by a memory corruption condition (heap-based buffer overflow), triggered when handling a crafted PowerPoint document—no public exploit is known, but Microsoft has released fixes for multiple Office and PowerPoint versions.

If you're affected

  • Full device compromise
  • Malware installation risk
  • Operational disruption
  • Business data theft risk

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

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

  1. OpenVAS check addedpatch available, record updated
  2. Record updatedrecord 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