Microsoft Office Remote Code Execution Vulnerability

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. May 12, 2017 · Catalog

   Detected

   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.

2. Feb 10, 2022 · CISA KEV

   Known exploited

   Apply updates per vendor instructions.

3. Aug 10, 2022 · CISA KEV

   Remediation due

   Apply updates per vendor instructions.

4. Jun 16, 2026 · Catalog

   Updated

   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.

Affected

• cpe microsoft/office2010
• cpe microsoft/office2013
• cpe microsoft/office2016
• vendor Microsoft Officeversion unspecified

Sources

• CISA KEVConfirmed exploitationCVE-2017-0262

  A remote code execution vulnerability exists in Microsoft Office.

  cisa.gov
• CVE.orgVulnerability recordCVE-2017-0262

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2017-0262

  30-day exploitation probability 81.0%

  first.org
• NIST NVDVulnerability recordCVE-2017-0262

  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.

  nvd.nist.gov

References

• Third Party Advisory · securityfocus.com
• CISA note · nvd.nist.gov
• Patch · portal.msrc.microsoft.com
• US Government Resource · cisa.gov