Threat Intelligence / CVE / CVE-2017-8570

CVE-2017-8570 — Microsoft Office 2007 SP3, Microsoft Office 2010 SP2, Microsoft Office 2013 SP1, and Microsoft Office 2016.

CISA KEV
CVSS v3.1 7.8 (HIGH) · EPSS 89.8% (higher than 99.7% of all scored CVEs) · Priority 9/10 · Published 2017-07-11

As of 2025-10-21, CVE-2017-8570 is a HIGH-severity vulnerability in Microsoft Office 2007 SP3, Microsoft Office 2010 SP2, Microsoft Office 2013 SP1, and Microsoft Office 2016., CVSS v3.1 7.8, EPSS 89.8% (99.7th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-02-25), with a US federal remediation deadline of 2022-08-25. Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2017-8570, most recently “Agent Tesla .NET Remote Access Trojan — Credential and Data Theft via Keylogging and MaaS Operations”.

Last updated: 2025-10-21

What is CVE-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.

Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3359 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.8 — HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (FIRST)
89.8% probability of exploitation in the next 30 days, higher than 99.7% of all scored CVEs
CISA KEV
Listed since 2022-02-25, federal remediation deadline 2022-08-25
Threadlinqs priority
9/10 — CISA KEV-listed, which Threadlinqs floors at 9
Published
2017-07-11, last modified 2025-10-21

Is CVE-2017-8570 being exploited?

CISA added CVE-2017-8570 to the Known Exploited Vulnerabilities catalog on 2022-02-25, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2022-08-25 under BOD 22-01. Weaponised exploit code for CVE-2017-8570 is publicly available. 8 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 43 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2017-8570

The record marks a vendor fix as available for CVE-2017-8570. Patch reference: https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8570. Vendor advisory: https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8570. Because CVE-2017-8570 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2022-08-25. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2017-8570

1 tracked threat in the Threadlinqs corpus references CVE-2017-8570, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Vulnerability database entry

Other references

Full detection coverage & IOCs for threats exploiting CVE-2017-8570 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence