CVE-2017-0070

HIGHNVD 7.58.8▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.8 because EPSS predicts 79% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
CISA-KEV: Not listedEPSS: 79%CVSS: 7.5Exploit: NoneExposed: 0

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

A remote code execution vulnerability exists in the way affected Microsoft scripting engines render when handling objects in memory in Microsoft browsers. These vulnerabilities could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. This vulnerability is different from those described in CVE-2017-0010, CVE-2017-0015, CVE-2017-0032, CVE-2017-0035, CVE-2017-0067, CVE-2017-0071, CVE-2017-0094, CVE-2017-0131, CVE-2017-0132, CVE-2017-0133, CVE-2017-0134, CVE-2017-0136, CVE-2017-0137, CVE-2017-0138, CVE-2017-0141, CVE-2017-0150, and CVE-2017-0151.

CVSS v3
7.5
EG Score
8.8(high)
EG Risk
76(Track)
EG Risk 76/100SSVC: Track

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
Severity88% × 45%
Exploitation79% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.5%
KEV
Not listed

Published

March 17, 2017

Last Modified

May 13, 2026

References (8)

Data Freshness Timeline

(refreshed 7× in last 7d / 20× 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.

  1. 2026-07-24 14:13 UTCEPSS rescore
  2. 2026-07-23 01:25 UTCEG score recompute▲ 1.30
  3. 2026-07-22 22:04 UTCEG score recompute
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-21 15:21 UTCEPSS rescore
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-16 16:59 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-12 05:43 UTCEPSS rescore
  13. 2026-07-12 05:43 UTCEPSS rescore
  14. 2026-07-09 19:06 UTCEPSS rescore
  15. 2026-07-06 16:24 UTCEPSS rescore
  16. 2026-07-06 16:24 UTCEPSS rescore
  17. 2026-06-30 23:19 UTCEPSS rescore
  18. 2026-06-30 23:19 UTCEPSS rescore
  19. 2026-06-27 03:05 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-23 21:30 UTCEPSS rescore
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 14:54 UTCEPSS rescore
Show 31 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-17 17:50 UTCEPSS rescore
  3. 2026-06-15 17:45 UTCEPSS rescore
  4. 2026-06-13 22:57 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-08 14:14 UTCEPSS rescore
  8. 2026-06-06 13:45 UTCEPSS rescore
  9. 2026-06-06 13:45 UTCEPSS rescore
  10. 2026-06-05 22:44 UTCEPSS rescore
  11. 2026-06-05 06:08 UTCEPSS rescore
  12. 2026-06-05 06:08 UTCEPSS rescore
  13. 2026-06-04 13:10 UTCEPSS rescore
  14. 2026-06-04 13:10 UTCEPSS rescore
  15. 2026-05-31 22:28 UTCEPSS rescore
  16. 2026-05-31 22:28 UTCEPSS rescore
  17. 2026-05-31 00:14 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-28 13:42 UTCEPSS rescore
  20. 2026-05-26 13:42 UTCEPSS rescore
  21. 2026-05-26 13:42 UTCEPSS rescore
  22. 2026-05-24 16:44 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-22 15:20 UTCEG score recompute
  25. 2026-05-22 15:20 UTCGHSA enrichment
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 22:37 UTCEPSS rescore
  28. 2026-05-20 22:37 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore
  30. 2026-05-18 21:30 UTCEPSS rescore
  31. 2026-05-18 21:30 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-41623✓ verified
    First seen Mar 16, 2017

    Microsoft Edge 38.14393.0.0 - JavaScript Engine Use-After-Free

    Open source ↗

Frequently asked(5)

What is CVE-2017-0070?
CVE-2017-0070 is a high vulnerability published on March 17, 2017. A remote code execution vulnerability exists in the way affected Microsoft scripting engines render when handling objects in memory in Microsoft browsers. These vulnerabilities could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An…
When was CVE-2017-0070 disclosed?
CVE-2017-0070 was first published in the National Vulnerability Database on March 17, 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-0070 actively exploited?
CVE-2017-0070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0070?
CVE-2017-0070 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.8.
How do I remediate CVE-2017-0070?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0070, 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-0070

Explore →

Is Your Infrastructure Affected by CVE-2017-0070?

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

Start Free Scan →Browse All CVEs