ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2017-8570

Microsoft Office Remote Code Execution Vulnerability

Published Jul 11, 2017 · catalog updated Jun 16, 2026 · Microsoft Office

Patch now

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

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
Severity
High7.8
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
89.89%
Remediation
Remediation guidance
Affected products
cpe microsoft/office · vendor Microsoft Office

Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0243.

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/office2007
  • cpe microsoft/office2010
  • cpe microsoft/office2013
  • cpe microsoft/office2016
  • vendor Microsoft Officeversion unspecified

How to fix CVE-2017-8570

What to do

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

Should you patch?

CVE-2017-8570 is in the CISA known-exploited catalog, due Aug 25, 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 2007, 2010, 2013, 2016. Apply updates per vendor instructions.

What should an analyst verify?

No weakness class is stored. EPSS 89.89%. The CISA KEV listing is the exploitation evidence. A public exploit reference is linked in Sources. That is not the same as confirmed exploitation. Use the source links for the original advisory.

Code

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

Timeline

Detection, updates, and resolution for this record.

  1. Jul 11, 2017 · Catalog

    Detected

    Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0243.

  2. Feb 25, 2022 · CISA KEV

    Known exploited

    Apply updates per vendor instructions.

  3. Aug 25, 2022 · CISA KEV

    Remediation due

    Apply updates per vendor instructions.

  4. Jun 16, 2026 · Catalog

    Updated

    Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0243.

Sources

  • CISA KEVConfirmed exploitationCVE-2017-8570

    A remote code execution vulnerability exists in Microsoft Office software when it fails to properly handle objects in memory.

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

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2017-8570

    30-day exploitation probability 89.9%

    first.org
  • Exploit DatabasePublic exploit reference44263

    Public archive entry. The exploit body is not stored here.

    exploit-db.com
  • NIST NVDVulnerability recordCVE-2017-8570

    Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0243.

    nvd.nist.gov
  • VulnCheck KEVConfirmed exploitationCVE-2017-8570

    A remote code execution vulnerability exists in Microsoft Office software when it fails to properly handle objects in memory.

    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.