Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2017-0262: Microsoft Office EPS Filter Type Confusion Remote Code Execution

Published May 12, 2017 · 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
EPSS81.0%100th percentile
CISA KEVYesAdded Feb 10, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2017-0262CWE-843

CVE-2017-0262 is a type-confusion vulnerability in the Encapsulated PostScript (EPS) filter of Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016. A malicious Office document containing embedded EPS content can trigger the flaw when opened. Exploitation uses a forged procedure object with the PostScript forall operator to control operand-stack values, followed by heap spraying and forged objects to disclose module-base information. A forged file object and the bytesavailable operator redirect execution into a ROP chain and shellcode. APT28 exploited the vulnerability as a zero-day in 2017, including chains with the separate Windows privilege-escalation vulnerability CVE-2017-0263.

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 enables attacker-controlled code execution during Office document processing. Observed exploitation involved a sandboxed EPS-processing context; another observed campaign executed its dropper within Word under the current user's privileges before privilege escalation. APT28 paired the flaw with CVE-2017-0263 to escape the EPS-processing sandbox or obtain SYSTEM privileges and install malware, including GAMEFISH and Seduploader. Those elevated privileges require the separate privilege-escalation vulnerability and are not an intrinsic consequence of CVE-2017-0262 alone.

Mitigation

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

Disable Office EPS processing and follow Microsoft's defense-in-depth guidance in security advisory ADV170005. Microsoft disabled EPS processing in its April 2017 Patch Tuesday updates, significantly reducing the effectiveness of this exploit.

Remediation

Patch, then assume compromise.

Apply Microsoft's security updates addressing CVE-2017-0262 to affected Office installations. Microsoft released a patch on a regular Patch Tuesday. Systems exposed to the observed exploit chain should also receive the Windows update addressing CVE-2017-0263.

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-2017-0262 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 Feb 10, 2022.
Is there a public exploit for CVE-2017-0262?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2017-0262.
Is there a patch for CVE-2017-0262?
Apply Microsoft's security updates addressing CVE-2017-0262 to affected Office installations. Microsoft released a patch on a regular Patch Tuesday.
What products are affected by CVE-2017-0262?
Microsoft Corporation Microsoft Office.
How severe is CVE-2017-0262?
CVE-2017-0262 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 81.0% (100th percentile) as of Oct 16, 2026.
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 evidence8Every report linking this CVE to a named adversary.
Associated malware3Malware 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 activity1Community discussion across Reddit, Mastodon, and other social sources.