Skip to main content
Mallory
CriticalVulnerability

CVE-2011-1269: Presentation Memory Corruption RCE Vulnerability in Microsoft PowerPoint

Published May 13, 2011 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v2
EPSS14.9%97th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2011-1269CWE-119

A memory corruption vulnerability exists in Microsoft PowerPoint 2002 SP3, 2003 SP3, 2007 SP2, Office 2004 and 2008 for Mac, Open XML File Format Converter for Mac, and Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats SP2. The vulnerability is due to unspecified function calls made during the parsing of PowerPoint files, where memory is not properly handled. This flaw can be triggered by a specially crafted PowerPoint document, leading to memory corruption and potential arbitrary code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code in the context of the user opening a malicious PowerPoint document. This could lead to full compromise of the affected system if the user has administrative privileges.

Mitigation

If you can’t patch tonight, do this now.

Users should avoid opening PowerPoint files from untrusted sources. Employing the principle of least privilege can limit the impact of exploitation. Additionally, consider using Office File Block policy settings to restrict opening of potentially dangerous file types.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft for all affected products. Ensure that all Office installations are updated to the latest supported service packs and security patches.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationMicrosoft Officeapplication
Microsoft CorporationOffice Compatibility Packapplication
Microsoft CorporationOpen Xml File Format Converterapplication
Microsoft CorporationPowerpointapplication
FAQ

Frequently asked questions

Is CVE-2011-1269 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2011-1269 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2011-1269?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2011-1269.
Is there a patch for CVE-2011-1269?
Apply the security updates provided by Microsoft for all affected products. Ensure that all Office installations are updated to the latest supported service packs and security patches.
What products are affected by CVE-2011-1269?
Microsoft Corporation Office Compatibility Pack, Microsoft Corporation Open Xml File Format Converter, Microsoft Corporation Powerpoint, and Microsoft Corporation Microsoft Office.
How severe is CVE-2011-1269?
CVE-2011-1269 has a CVSS v2 score of 9.3 (Critical) and an EPSS score of 14.9% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.