CVE-2017-8570

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-02-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 90%CVSS: 7.8Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
90%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 11, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8570
generic

GitHub - tezukanice/Office8570: CVE20178570 · GitHub

https://github.com/tezukanice/Office8570
generic🔴 Active Exploitation

GitHub - rxwx/CVE-2017-8570: Proof of Concept exploit for CVE-2017-8570 · GitHub

https://github.com/rxwx/CVE-2017-8570
generic

GitHub - ParsingTeam/ppsx-file-generator: CVE-2017-8570 Exploit · GitHub

https://github.com/ParsingTeam/ppsx-file-generator
generic
http://www.securityfocus.com/bid/99445

Vendor Advisories for CVE-2017-8570(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 89× in last 7d / 385× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 1,607 total refreshes for this CVE.

  1. 2026-10-04 11:05 UTCVendor advisory
  2. 2026-10-04 11:05 UTCGHSA enrichment
  3. 2026-10-04 07:14 UTCVendor advisory
  4. 2026-10-04 07:14 UTCGHSA enrichment
  5. 2026-10-04 03:23 UTCVendor advisory
  6. 2026-10-04 03:23 UTCGHSA enrichment
  7. 2026-10-03 23:32 UTCVendor advisory
  8. 2026-10-03 23:32 UTCGHSA enrichment
  9. 2026-10-03 19:41 UTCVendor advisory
  10. 2026-10-03 19:41 UTCGHSA enrichment
  11. 2026-10-03 15:51 UTCVendor advisory
  12. 2026-10-03 15:50 UTCGHSA enrichment
  13. 2026-10-03 12:00 UTCVendor advisory
  14. 2026-10-03 12:00 UTCGHSA enrichment
  15. 2026-10-03 08:08 UTCVendor advisory
  16. 2026-10-03 08:08 UTCGHSA enrichment
  17. 2026-10-03 04:14 UTCVendor advisory
  18. 2026-10-03 04:14 UTCGHSA enrichment
  19. 2026-10-03 00:23 UTCVendor advisory
  20. 2026-10-03 00:23 UTCGHSA enrichment
  21. 2026-10-02 20:32 UTCVendor advisory
  22. 2026-10-02 20:32 UTCGHSA enrichment
  23. 2026-10-02 16:40 UTCVendor advisory
  24. 2026-10-02 16:40 UTCGHSA enrichment
  25. 2026-10-02 12:45 UTCVendor advisory
Show 75 more
  1. 2026-10-02 12:45 UTCGHSA enrichment
  2. 2026-10-02 08:54 UTCVendor advisory
  3. 2026-10-02 08:54 UTCGHSA enrichment
  4. 2026-10-02 05:03 UTCVendor advisory
  5. 2026-10-02 05:03 UTCGHSA enrichment
  6. 2026-10-02 01:12 UTCVendor advisory
  7. 2026-10-02 01:12 UTCGHSA enrichment
  8. 2026-10-01 21:21 UTCVendor advisory
  9. 2026-10-01 21:21 UTCGHSA enrichment
  10. 2026-10-01 17:31 UTCVendor advisory
  11. 2026-10-01 17:30 UTCGHSA enrichment
  12. 2026-10-01 13:39 UTCVendor advisory
  13. 2026-10-01 13:39 UTCGHSA enrichment
  14. 2026-10-01 09:48 UTCVendor advisory
  15. 2026-10-01 09:48 UTCGHSA enrichment
  16. 2026-10-01 05:57 UTCVendor advisory
  17. 2026-10-01 05:57 UTCGHSA enrichment
  18. 2026-10-01 02:06 UTCVendor advisory
  19. 2026-10-01 02:06 UTCGHSA enrichment
  20. 2026-09-30 22:14 UTCVendor advisory
  21. 2026-09-30 22:14 UTCGHSA enrichment
  22. 2026-09-30 18:23 UTCEG score recompute
  23. 2026-09-30 18:23 UTCGHSA enrichment
  24. 2026-09-30 14:59 UTCEPSS rescore
  25. 2026-09-30 14:32 UTCVendor advisory
  26. 2026-09-30 14:32 UTCGHSA enrichment
  27. 2026-09-30 10:40 UTCVendor advisory
  28. 2026-09-30 10:40 UTCGHSA enrichment
  29. 2026-09-30 06:49 UTCVendor advisory
  30. 2026-09-30 06:49 UTCGHSA enrichment
  31. 2026-09-30 02:57 UTCVendor advisory
  32. 2026-09-30 02:57 UTCGHSA enrichment
  33. 2026-09-29 23:06 UTCVendor advisory
  34. 2026-09-29 23:05 UTCGHSA enrichment
  35. 2026-09-29 19:12 UTCVendor advisory
  36. 2026-09-29 19:12 UTCGHSA enrichment
  37. 2026-09-29 15:19 UTCVendor advisory
  38. 2026-09-29 15:19 UTCGHSA enrichment
  39. 2026-09-29 11:28 UTCVendor advisory
  40. 2026-09-29 11:28 UTCGHSA enrichment
  41. 2026-09-29 07:37 UTCVendor advisory
  42. 2026-09-29 07:37 UTCGHSA enrichment
  43. 2026-09-29 03:47 UTCVendor advisory
  44. 2026-09-29 03:47 UTCGHSA enrichment
  45. 2026-09-28 23:56 UTCEG score recompute
  46. 2026-09-28 23:56 UTCVendor advisory
  47. 2026-09-28 23:55 UTCGHSA enrichment
  48. 2026-09-28 20:04 UTCVendor advisory
  49. 2026-09-28 20:04 UTCGHSA enrichment
  50. 2026-09-28 16:08 UTCVendor advisory
  51. 2026-09-28 16:08 UTCGHSA enrichment
  52. 2026-09-28 12:13 UTCVendor advisory
  53. 2026-09-28 12:13 UTCGHSA enrichment
  54. 2026-09-28 08:22 UTCVendor advisory
  55. 2026-09-28 08:22 UTCGHSA enrichment
  56. 2026-09-28 04:29 UTCVendor advisory
  57. 2026-09-28 04:29 UTCGHSA enrichment
  58. 2026-09-28 00:38 UTCVendor advisory
  59. 2026-09-28 00:38 UTCGHSA enrichment
  60. 2026-09-27 21:51 UTCCISA KEV update
  61. 2026-09-27 20:47 UTCVendor advisory
  62. 2026-09-27 20:47 UTCGHSA enrichment
  63. 2026-09-27 16:56 UTCVendor advisory
  64. 2026-09-27 16:56 UTCGHSA enrichment
  65. 2026-09-27 13:05 UTCVendor advisory
  66. 2026-09-27 13:05 UTCGHSA enrichment
  67. 2026-09-27 09:14 UTCVendor advisory
  68. 2026-09-27 09:14 UTCGHSA enrichment
  69. 2026-09-27 05:23 UTCVendor advisory
  70. 2026-09-27 05:23 UTCGHSA enrichment
  71. 2026-09-27 01:31 UTCVendor advisory
  72. 2026-09-27 01:30 UTCGHSA enrichment
  73. 2026-09-26 21:37 UTCVendor advisory
  74. 2026-09-26 21:37 UTCGHSA enrichment
  75. 2026-09-26 17:46 UTCVendor advisory

Publicly available exploits

(5 references)

Working exploit code is in the public domain (4 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCDrac0nids/CVE-2017-8570
    First seen Jan 3, 2019

    ## 在kali中自动化生成cve-2017-8570的恶意ppsx文件和配置msf监听

    Open source ↗
  • GitHub PoCSwordSheath/CVE-2017-8570
    First seen Apr 8, 2018

    CVE-2017-8570生成脚本(CVE-2017-0199另一种利用方式)

    Open source ↗
  • Exploit-DBEDB-44263
    First seen Jan 9, 2018

    Microsoft Office - 'Composite Moniker Remote Code Execution

    Open source ↗
  • GitHub PoCrxwx/CVE-2017-8570
    First seen Jan 9, 2018

    Proof of Concept exploit for CVE-2017-8570

    Open source ↗
  • GitHub PoCtemesgeny/ppsx-file-generator
    First seen Jul 24, 2017

    ppsx file generator for cve-2017-8570 (based on bhdresh/cve-2017-8570)

    Open source ↗

Frequently asked(6)

What is CVE-2017-8570?
CVE-2017-8570 is a critical vulnerability published on July 11, 2017. 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.
When was CVE-2017-8570 disclosed?
CVE-2017-8570 was first published on July 11, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-8570 actively exploited?
Yes. CISA added CVE-2017-8570 to the Known Exploited Vulnerabilities catalog on February 25, 2022, affecting Microsoft Office. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2017-8570?
CVE-2017-8570 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2017-8570?
CVE-2017-8570 affects Microsoft Office.
How do I remediate CVE-2017-8570?
A fix for CVE-2017-8570 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-8570 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-8570

Explore →

Is Your Infrastructure Affected by CVE-2017-8570?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs