Microsoft Edge in Microsoft Windows 10 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8634, CVE-2017-8635, CVE-2017-8636, CVE-2017-8638, CVE-2017-8639, CVE-2017-8640, CVE-2017-8641, CVE-2017-8645, CVE-2017-8646, CVE-2017-8647, CVE-2017-8655, CVE-2017-8657, CVE-2017-8670, CVE-2017-8671, CVE-2017-8672, and CVE-2017-8674.
CVE-2017-8656
HIGHNVD 7.57.5—Weaponized
EchelonGraph scoreMEDIUM confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-17. NVD baseline CVSS 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
- High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS: 69%CVSS: 7.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 99.3%
- KEV
- Not listed
Published
August 8, 2017
Last Modified
May 13, 2026
References (8)
- secure@microsofthttp://www.securityfocus.com/bid/100033
- secure@microsofthttp://www.securitytracker.com/id/1039095
- secure@microsofthttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8656
- secure@microsofthttps://www.exploit-db.com/exploits/42464/
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/100033
- af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1039095
- af854a3a-2127-422b-91ae-364da2661108https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8656
- af854a3a-2127-422b-91ae-364da2661108https://www.exploit-db.com/exploits/42464/
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.
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-42464✓ verifiedFirst seen Aug 17, 2017
Microsoft Edge Chakra - 'PreVisitCatch' Missing Call
Open source ↗
Frequently asked(5)
What is CVE-2017-8656?
CVE-2017-8656 is a high vulnerability published on August 8, 2017. Microsoft Edge in Microsoft Windows 10 1607, 1703, and Windows Server 2016 allows an attacker to execute arbitrary code in the context of the current user due to the way that Microsoft browser JavaScript engines render content when handling objects in memory, aka "Scripting Engine Memory Corruption…
When was CVE-2017-8656 disclosed?
CVE-2017-8656 was first published in the National Vulnerability Database on August 8, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-8656 actively exploited?
CVE-2017-8656 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-8656?
CVE-2017-8656 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-8656?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8656, 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-8656
Is Your Infrastructure Affected by CVE-2017-8656?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.