CVE-2017-5070

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-06-08), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.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
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 31%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.

CVSS v3
8.8
EG Score
9.0(high)
EPSS
98.1%
KEV
⚠ Exploited

Published

October 27, 2017

Last Modified

April 21, 2026

Advisory Details (5)

Auto-updated May 2, 2026
Patch available. Sources: redhat.
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html
redhat Patch Available

Affected: Red Hat Enterprise Linux 6 Supplementary.

https://access.redhat.com/errata/RHSA-2017:1399
generic
http://www.securityfocus.com/bid/98861
generic

Chromium: Multiple vulnerabilities (GLSA 201706-20) — Gentoo security

https://security.gentoo.org/glsa/201706-20
generic
https://crbug.com/722756

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatchromium-browser-0:59.0.3071.86-1.el6_92017-06-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

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 142× in last 7d / 598× 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 961 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2017-5070?
CVE-2017-5070 is a high vulnerability published on October 27, 2017. Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
When was CVE-2017-5070 disclosed?
CVE-2017-5070 was first published in the National Vulnerability Database on October 27, 2017, with the most recent update on April 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5070 actively exploited?
Yes. CISA added CVE-2017-5070 to the Known Exploited Vulnerabilities catalog on June 8, 2022, affecting Google Chromium V8. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2017-5070?
CVE-2017-5070 has a CVSS v3 base score of 8.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-5070?
CVE-2017-5070 affects Google Chromium V8. 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-5070?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5070, 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-5070

Explore →

Is Your Infrastructure Affected by CVE-2017-5070?

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

Start Free Scan →Browse All CVEs