CVE-2017-8570

HIGHNVD 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
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 90%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.0(high)
EPSS
99.8%
KEV
⚠ Exploited

Published

July 11, 2017

Last Modified

April 22, 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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 131× in last 7d / 559× 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 738 total refreshes for this CVE.

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

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 high 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 in the National Vulnerability Database on July 11, 2017, with the most recent update on April 22, 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 patching attention.
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.
Which products are affected by CVE-2017-8570?
CVE-2017-8570 affects Microsoft Office. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2017-8570?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8570, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs