Skip to content
Server Security Center
KEVhigh8.8

CVE-2009-0556: Microsoft Office PowerPoint Code Injection

Microsoft Office · listed in the CISA catalog of actively exploited vulnerabilities since 2026-01-07.

CVSS v3.1 (CISA ADP)
8.8
high
EPSS (exploit probability, 30 days)
67%
higher than 99.3% of all CVEs
Added to CISA KEV
2026-01-07
US federal due date 2026-01-28
Automatable (CISA SSVC)
no
technical impact: total

CVE-2009-0556 explained

CVE-2009-0556 is a memory corruption flaw in Microsoft Office PowerPoint, caused by an invalid index value in a crafted PowerPoint file. Opening such a file can let a remote attacker run arbitrary code. The description says it was exploited in the wild in April 2009, and CISA lists it as a known exploited vulnerability.

Impact

An attacker who persuades a user to open a crafted PowerPoint file can execute arbitrary code with high impact on confidentiality, integrity and availability. No privileges are needed, but user interaction is required. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so attacks need steps such as delivering the file to each victim.

Who is affected

The description names Microsoft Office PowerPoint 2000 SP3, 2002 SP3 and 2003 SP3, and PowerPoint in Microsoft Office 2004 for Mac. The structured CVE record lists no affected version ranges for Microsoft Office. It also names no fixed version. Check the Microsoft advisory for the updates that address this issue.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Office PowerPoint 2000 SP3, 2002 SP3, and 2003 SP3, and PowerPoint in Microsoft Office 2004 for Mac, allows remote attackers to execute arbitrary code via a PowerPoint file with an OutlineTextRefAtom containing an an invalid index value that triggers memory corruption, as exploited in the wild in April 2009 by Exploit:Win32/Apptom.gen, aka "Memory Corruption Vulnerability."

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
  • CISA's deadline for US federal agencies: 2026-01-28 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify systems running PowerPoint 2000, 2002, 2003 or Office 2004 for Mac.
  2. Apply the Microsoft security update or mitigations described in the vendor advisory.
  3. Replace these old PowerPoint versions with currently supported Office releases where possible.
  4. Warn users not to open PowerPoint files from untrusted or unexpected sources.
  5. Check systems that opened suspicious PowerPoint files for signs of compromise.

The CVE record names no fixed version. Follow the Microsoft advisory for updates and mitigations. CISA's required action is to apply mitigations per vendor instructions, follow BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Until then, block or closely screen PowerPoint files from untrusted sources.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-94 Improper Control of Generation of Code ('Code Injection')

Questions about CVE-2009-0556

Is this vulnerability being exploited?
Yes. The description says it was exploited in the wild in April 2009, and CISA added it to its Known Exploited Vulnerabilities catalog on 2026-01-07. Whether it is used in ransomware campaigns is unknown.
Can it be exploited without user action?
No. A user must open a crafted PowerPoint file. CISA rates it as not automatable.
What is the deadline for US federal agencies?
CISA set a due date of 2026-01-28 for federal agencies to apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.