Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2015-2545: Microsoft Office Malformed EPS File Vulnerability

Published Sep 9, 2015 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS85.9%100th percentile
CISA KEVYesAdded Mar 3, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2015-2545CWE-119

CVE-2015-2545 is an EPS parsing vulnerability in Microsoft Office 2007 SP3, 2010 SP2, 2013 SP1, and 2013 RT SP1. Processing a specially crafted Encapsulated PostScript image permits arbitrary code execution. Attackers have embedded malicious EPS objects in Office documents and MHTML web archives delivered through spear phishing. Exploitation was observed in August 2015 and subsequently adopted by multiple espionage groups and cybercriminal campaigns.

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 permits attacker-controlled code execution through Microsoft Office. Observed attacks used this capability to deploy backdoors, including TidePool and SPIVY, enabling remote command execution and data access. SYSTEM-level compromise in documented exploit chains required a separate privilege-escalation vulnerability, such as CVE-2015-2546 or CVE-2015-1701; it is not established as a direct consequence of CVE-2015-2545 alone.

Mitigation

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

Prevent Office applications from opening untrusted documents and attachments, particularly documents containing embedded EPS content. Apply Microsoft guidance for disabling or restricting EPS filter processing where patch deployment is not immediately possible, enforce Protected View and macro/document-application controls, and use email gateway filtering and attachment sandboxing to identify malformed or embedded EPS content.

Remediation

Patch, then assume compromise.

Apply Microsoft's MS15-099 security update, released on September 8, 2015, to affected Office installations.

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
FAQ

Frequently asked questions

Is CVE-2015-2545 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 3, 2022.
Is there a public exploit for CVE-2015-2545?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2015-2545.
Is there a patch for CVE-2015-2545?
Apply Microsoft's MS15-099 security update, released on September 8, 2015, to affected Office installations.
What products are affected by CVE-2015-2545?
Microsoft Corporation Microsoft Office.
How severe is CVE-2015-2545?
CVE-2015-2545 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 85.9% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

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

View more in app →
+10 more in the timeline. Sign up to see them
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 evidence15Every report linking this CVE to a named adversary.
Associated malware13Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, 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.