Microsoft Office Remote Code Execution Vulnerability
Exploited in the wild as a zero-day, in CISA KEV since 10 Feb 2022 (due 10 Aug 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-0261 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. It was exploited as a zero-day before a fix was available and is listed in CISA KEV.
Why it mattersConfirmed exploited in the wild as a zero-day, with EPSS of 81%, so unpatched Office users face high risk of remote code execution.
ActionApply Microsoft's Office security updates for the listed versions; check for exploit indicators where legacy Office is in use.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Microsoft | Office | =Microsoft Office 2010 SP2, Office 2013 SP1, and Office 2016 |
Exploit evidence
1 public sources
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Office, strongest first
Embed
A live severity badge for an advisory, README or ticket