How to check if you are exposed to CVE-2017-8570
- Find every Microsoft Office system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
- Compare each version with the fixed versions in the vendor advisory. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
- Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2017-8570.
US federal agencies had to fix this by 2022-08-25. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.
Timeline
- · Added to CISA's Known Exploited Vulnerabilities catalog
- · Fix-by date for US federal agencies, passed 1,529 days ago
More exploited Microsoft vulnerabilities
CISA lists 390 exploited Microsoft vulnerabilities. The closest matches:
- CVE-2009-0238Microsoft Office Remote Code ExecutionAdded 2026-04-14
- CVE-2026-21514Microsoft Office Word Reliance on Untrusted Inputs in a Security Decision VulnerabilityAdded 2026-02-10
- CVE-2026-21509Microsoft Office Security Feature Bypass VulnerabilityAdded 2026-01-26
- CVE-2009-0556Microsoft Office PowerPoint Code Injection VulnerabilityAdded 2026-01-07
- CVE-2007-0671Microsoft Office Excel Remote Code Execution VulnerabilityAdded 2025-08-12
- CVE-2023-23397Microsoft Office Outlook Privilege Escalation VulnerabilityAdded 2023-03-14
- CVE-2023-21715Microsoft Office Publisher Security Feature Bypass VulnerabilityAdded 2023-02-14
- CVE-2013-1331Microsoft Office Buffer Overflow VulnerabilityAdded 2022-06-08
Keep going
Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.10.30); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.