CVE-2009-0556: Legacy PowerPoint file code execution

Quick Answer

CVE-2009-0556 corrupts memory when an affected PowerPoint version reads an invalid index in a crafted file. The user must open the file; email delivery alone is not execution. Code runs with the logged-on user's rights. Identify the specific legacy versions below, preserve document and endpoint evidence, and migrate unsupported Office. The historical patch is not a current support guarantee.

Evidence check: Vendor evidence and unresolved limits are described below. CISA KEV catalog 2026.10.02 was checked October 2. Catalog additions, vendor publication dates and update releases are separate events. No exploit, installation or recovery test is claimed.

Context

Status At A Glance

Product scope	Microsoft — Office
CVE	CVE-2009-0556
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-01-07
Vendor severity	Critical: PowerPoint 2000 SP3. Important: PowerPoint 2002 SP3, PowerPoint 2003 SP3 and Office 2004 for Mac (CVE-0556 column).
CVSS	No numerical CVSS supplied by the checked MS09-017 bulletin.
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-94
Federal remediation date	2026-01-28 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Microsoft Office PowerPoint Code Injection Vulnerability. Microsoft Office PowerPoint contains a code injection vulnerability that allows remote attackers to execute arbitrary code via a PowerPoint file with an OutlineTextRefAtom containing an invalid index value that triggers memory corruption. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Legacy Microsoft Office and PowerPoint releases listed in Microsoft bulletin MS09-017.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Office asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
4. Remediate. Find affected legacy PowerPoint installations, apply the historical security update where applicable, and migrate unsupported Office versions to a supported release.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

A malformed PowerPoint file can trigger memory corruption and arbitrary code execution. CISA added the CVE to KEV on 2026-01-07; review document-delivery and endpoint evidence on any matching legacy host.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Microsoft's CVE-2009-0556 FAQ reports limited, targeted attempts to exploit the flaw at bulletin publication. CISA's January 7, 2026 KEV addition is a separate catalog event, not the date this legacy vulnerability first became exploitable.

CISA statement: CVE-2009-0556 was added to KEV on 2026-01-07. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Microsoft security advisory
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2009-0556 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.