Findings

CVE-2017-8509

A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability".

Published Jun 15, 2017 · updated Oct 15, 2026 · microsoft office

A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.

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. Jun 15, 2017 · NIST NVD

    Detected

    A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.

  2. Oct 15, 2026 · NIST NVD

    Updated

    A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-8506.

Affected

  • cpe microsoft/office2007
  • cpe microsoft/office2010
  • cpe microsoft/office2013
  • cpe microsoft/office2016
  • cpe microsoft/office compatibility packversion unspecified
  • cpe microsoft/office web apps2010
  • cpe microsoft/office web apps server2013
  • cpe microsoft/onenote2010

Sources

  • CVE.orgVulnerability recordCVE-2017-8509

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2017-8509

    A remote code execution vulnerability exists in Microsoft Office when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8510, CVE-2017-8511, CVE-2017-8512, CVE-2017-0260, and CVE-2017-850

    nvd.nist.gov

References

CVE-2017-8509 · ZeroDay Findings