CVE-2017-0261

published 9 May 2017 · updated 21 Oct 2025

Microsoft Office Remote Code Execution Vulnerability

10.0CriticalCVSS 7.8EPSS 78%CISA KEV · due 24 Mar 2022Zero-day

Exploited in the wild as a zero-day, in CISA KEV since 3 Mar 2022 (due 24 Mar 2022). No fixed version is recorded.

Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0262 and CVE-2017-0281.

Briefing

Written from the sources below · deepseek-v4.1-flash

Microsoft Office 2010 SP2, 2013 SP1, and 2016 fail to properly handle objects in memory, allowing remote code execution. The issue affects users of those Office versions.

Why it mattersIt was exploited as a zero-day and is in CISA KEV with high EPSS, so unpatched Office installs face active attack risk.

ActionApply the vendor fix for the affected Office version and check for exploitation indicators.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MicrosoftOffice=Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016

Exploit evidence

1 public sources

kev

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Office, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2017-0261 severity on Zeptric[![CVE-2017-0261](https://zeptric.io/badge/cve/CVE-2017-0261.svg)](https://zeptric.io/cve/CVE-2017-0261)