Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.2987.108 for Android allowed a remote attacker to execute arbitrary code via a crafted HTML page.
CVE-2017-5030
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.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 98.5%
- KEV
- ⚠ Exploited
Published
April 24, 2017
Last Modified
April 21, 2026
Advisory Details (7)
Auto-updated May 2, 2026[SECURITY] [DSA 3810-1] chromium-browser security update
http://www.debian.org/security/2017/dsa-3810Chromium: Multiple vulnerabilities (GLSA 201704-02) — Gentoo security
https://security.gentoo.org/glsa/201704-02Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2017/03/stable-channel-update-for-desktop.htmlPatch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | liboxideqtcore0 (1.21.5-0ubuntu0.16.10.1) @ yakkety | 2026-07-22 | ubuntu |
| redhat | chromium-browser-0:57.0.2987.98-1.el6 | 2017-03-14 | redhat |
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
(2)
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 105× in last 7d / 437× 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 810 total refreshes for this CVE.
- 2026-07-23 01:29 UTCEG score recompute
- 2026-07-22 23:59 UTCEG score recompute
- 2026-07-22 23:59 UTCVendor advisory
- 2026-07-22 23:59 UTCGHSA enrichment
- 2026-07-22 22:09 UTCEG score recompute
- 2026-07-22 20:17 UTCVendor advisory
- 2026-07-22 20:17 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:25 UTCEG score recompute
- 2026-07-22 16:25 UTCVendor advisory
- 2026-07-22 16:25 UTCGHSA enrichment
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 12:39 UTCVendor advisory
- 2026-07-22 12:39 UTCGHSA enrichment
- 2026-07-22 08:56 UTCVendor advisory
- 2026-07-22 08:56 UTCGHSA enrichment
- 2026-07-22 05:13 UTCVendor advisory
- 2026-07-22 05:13 UTCGHSA enrichment
- 2026-07-22 00:54 UTCVendor advisory
- 2026-07-22 00:53 UTCGHSA enrichment
- 2026-07-21 18:20 UTCVendor advisory
- 2026-07-21 18:20 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 14:37 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-21 14:37 UTCGHSA enrichment
- 2026-07-21 10:55 UTCVendor advisory
- 2026-07-21 10:55 UTCGHSA enrichment
- 2026-07-21 07:12 UTCVendor advisory
- 2026-07-21 07:12 UTCGHSA enrichment
- 2026-07-21 03:31 UTCVendor advisory
- 2026-07-21 03:31 UTCGHSA enrichment
- 2026-07-20 23:49 UTCVendor advisory
- 2026-07-20 23:49 UTCGHSA enrichment
- 2026-07-20 20:06 UTCEG score recompute
- 2026-07-20 20:06 UTCVendor advisory
- 2026-07-20 20:06 UTCGHSA enrichment
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 16:24 UTCVendor advisory
- 2026-07-20 16:24 UTCGHSA enrichment
- 2026-07-20 12:42 UTCVendor advisory
- 2026-07-20 12:41 UTCGHSA enrichment
- 2026-07-20 08:59 UTCVendor advisory
- 2026-07-20 08:59 UTCGHSA enrichment
- 2026-07-20 05:18 UTCVendor advisory
- 2026-07-20 05:17 UTCGHSA enrichment
- 2026-07-20 01:36 UTCVendor advisory
- 2026-07-20 01:36 UTCGHSA enrichment
- 2026-07-19 21:54 UTCVendor advisory
- 2026-07-19 21:54 UTCGHSA enrichment
- 2026-07-19 18:12 UTCVendor advisory
- 2026-07-19 18:12 UTCGHSA enrichment
- 2026-07-19 14:30 UTCVendor advisory
- 2026-07-19 14:30 UTCGHSA enrichment
- 2026-07-19 10:49 UTCVendor advisory
- 2026-07-19 10:48 UTCGHSA enrichment
- 2026-07-19 07:06 UTCVendor advisory
- 2026-07-19 07:06 UTCGHSA enrichment
- 2026-07-19 03:24 UTCEG score recompute
- 2026-07-19 03:24 UTCVendor advisory
- 2026-07-19 03:24 UTCGHSA enrichment
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 23:42 UTCVendor advisory
- 2026-07-18 23:42 UTCGHSA enrichment
- 2026-07-18 20:00 UTCVendor advisory
- 2026-07-18 20:00 UTCGHSA enrichment
- 2026-07-18 16:19 UTCVendor advisory
- 2026-07-18 16:19 UTCGHSA enrichment
- 2026-07-18 12:37 UTCEG score recompute
- 2026-07-18 12:37 UTCVendor advisory
- 2026-07-18 12:37 UTCGHSA enrichment
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-18 08:55 UTCVendor advisory
- 2026-07-18 08:55 UTCGHSA enrichment
- 2026-07-18 05:13 UTCVendor advisory
- 2026-07-18 05:13 UTCGHSA enrichment
- 2026-07-18 01:31 UTCVendor advisory
- 2026-07-18 01:31 UTCGHSA enrichment
- 2026-07-17 21:49 UTCVendor advisory
- 2026-07-17 21:49 UTCGHSA enrichment
- 2026-07-17 18:08 UTCVendor advisory
- 2026-07-17 18:08 UTCGHSA enrichment
- 2026-07-17 14:26 UTCVendor advisory
- 2026-07-17 14:26 UTCGHSA enrichment
- 2026-07-17 10:44 UTCVendor advisory
- 2026-07-17 10:44 UTCGHSA enrichment
- 2026-07-17 07:02 UTCEG score recompute
- 2026-07-17 07:02 UTCVendor advisory
- 2026-07-17 07:02 UTCGHSA enrichment
- 2026-07-17 03:19 UTCVendor advisory
- 2026-07-17 03:19 UTCGHSA enrichment
- 2026-07-16 23:37 UTCVendor advisory
- 2026-07-16 23:37 UTCGHSA enrichment
- 2026-07-16 19:56 UTCVendor advisory
- 2026-07-16 19:56 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:14 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-125
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-2015-9290EG 9.8CRITICAL
- CVE-2016-10749EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS 96%CRITICAL
- CVE-2014-3180EG 9.1CRITICAL
- CVE-2014-1508EG 9.1EPSS 90%CRITICAL
- CVE-2016-5198NVD 8.8EG 9.0 KEVEPSS 98%HIGH
- CVE-2016-4523NVD 7.5EG 9.0 KEVEPSS 98%HIGH
Frequently asked(6)
What is CVE-2017-5030?
When was CVE-2017-5030 disclosed?
Is CVE-2017-5030 actively exploited?
What is the CVSS score of CVE-2017-5030?
Which products are affected by CVE-2017-5030?
How do I remediate CVE-2017-5030?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-5030
Is Your Infrastructure Affected by CVE-2017-5030?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.