CVE-2017-8601

HIGHNVD 7.58.5▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.5 because EPSS predicts 67% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.5EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 67%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 67%CVSS: 7.5Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

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

Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engine fails to render when handling objects in memory in Microsoft Edge, aka "Scripting Engine Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8596, CVE-2017-8610, CVE-2017-8618, CVE-2017-8619, CVE-2017-8603, CVE-2017-8604, CVE-2017-8605, CVE-2017-8606, CVE-2017-8607, CVE-2017-8608, CVE-2017-8598 and CVE-2017-8609.

CVSS v3
7.5
EG Score
8.5HIGHhigh confidence
EG Risk
70
EG Risk 70/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
Severity85% × 45%
Exploitation67% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
67%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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

References (8)

Vendor Advisories for CVE-2017-8601(1)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

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

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-42479✓ verified
    First seen Aug 17, 2017

    Microsoft Edge 40.15063.0.0 Chakra - Incorrect JIT Optimization with TypedArray Setter #3

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-8601?
CVE-2017-8601 is a high vulnerability published on July 11, 2017. Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to execute arbitrary code in the context of the current user when the JavaScript engine fails to render when handling objects in memory in Microsoft Edge, aka "Scripting Engine Memory…
When was CVE-2017-8601 disclosed?
CVE-2017-8601 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-8601 actively exploited?
CVE-2017-8601 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 67% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-8601?
CVE-2017-8601 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5 (HIGH).
How do I remediate CVE-2017-8601?
No fix for CVE-2017-8601 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2017-8601 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-8601?

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

Book a Demo →Browse All CVEs