ZeroDay Findings
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2017-0262

Microsoft Office Remote Code Execution Vulnerability

Published May 9, 2017 · catalog updated Jun 16, 2026 · Microsoft Office

Patch now

CVE-2017-0262 is in the CISA known-exploited catalog, due Aug 10, 2022. Confirm Microsoft Office against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Severity
High7.8
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
81.01%
Remediation
Remediation guidance
Affected products
cpe microsoft/office · vendor Microsoft Office

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

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

How to fix CVE-2017-0262

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2017-0262 is in the CISA known-exploited catalog, due Aug 10, 2022. Confirm Microsoft Office against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Compare what you have installed with 2010, 2013, 2016. Apply updates per vendor instructions.

What should an analyst verify?

No weakness class is stored. EPSS 81.01%. The CISA KEV listing is the exploitation evidence. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

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.

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
  • VulnCheck KEVConfirmed exploitationCVE-2017-0262

    A remote code execution vulnerability exists in Microsoft Office.

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.