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 PROB
- 41%
- EPSS %ILE
- 99%
- KEV
- ⚠ Exploited
Published
April 24, 2017
Last Modified
June 17, 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-09-25 | 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.
Affected Packages
(1 across 1 ecosystem)
Debian:8(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium-browser | 41.0.2272.118-1 ... 56.0.2924.76-5 (92 versions) | 57.0.2987.98-1~deb8u1 | — |
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 106× in last 7d / 447× 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 1,731 total refreshes for this CVE.
- 2026-09-25 16:10 UTCVendor advisory
- 2026-09-25 16:10 UTCGHSA enrichment
- 2026-09-25 14:55 UTCCISA KEV update
- 2026-09-25 12:27 UTCVendor advisory
- 2026-09-25 12:27 UTCGHSA enrichment
- 2026-09-25 08:46 UTCVendor advisory
- 2026-09-25 08:45 UTCGHSA enrichment
- 2026-09-25 05:04 UTCVendor advisory
- 2026-09-25 05:04 UTCGHSA enrichment
- 2026-09-25 01:23 UTCVendor advisory
- 2026-09-25 01:23 UTCGHSA enrichment
- 2026-09-24 21:41 UTCVendor advisory
- 2026-09-24 21:41 UTCGHSA enrichment
- 2026-09-24 19:31 UTCCISA KEV update
- 2026-09-24 17:59 UTCVendor advisory
- 2026-09-24 17:59 UTCGHSA enrichment
- 2026-09-24 14:18 UTCEG score recompute
- 2026-09-24 14:18 UTCVendor advisory
- 2026-09-24 14:18 UTCGHSA enrichment
- 2026-09-24 13:59 UTCEPSS rescore
- 2026-09-24 10:36 UTCVendor advisory
- 2026-09-24 10:36 UTCGHSA enrichment
- 2026-09-24 06:52 UTCVendor advisory
- 2026-09-24 06:52 UTCGHSA enrichment
- 2026-09-24 03:11 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-24 03:11 UTCGHSA enrichment
- 2026-09-23 23:29 UTCVendor advisory
- 2026-09-23 23:29 UTCGHSA enrichment
- 2026-09-23 19:48 UTCVendor advisory
- 2026-09-23 19:48 UTCGHSA enrichment
- 2026-09-23 16:06 UTCEG score recompute
- 2026-09-23 16:06 UTCVendor advisory
- 2026-09-23 16:06 UTCGHSA enrichment
- 2026-09-23 12:25 UTCVendor advisory
- 2026-09-23 12:25 UTCGHSA enrichment
- 2026-09-23 08:43 UTCVendor advisory
- 2026-09-23 08:43 UTCGHSA enrichment
- 2026-09-23 05:02 UTCVendor advisory
- 2026-09-23 05:02 UTCGHSA enrichment
- 2026-09-23 01:20 UTCVendor advisory
- 2026-09-23 01:20 UTCGHSA enrichment
- 2026-09-22 21:38 UTCVendor advisory
- 2026-09-22 21:38 UTCGHSA enrichment
- 2026-09-22 19:36 UTCCISA KEV update
- 2026-09-22 17:56 UTCEG score recompute
- 2026-09-22 17:56 UTCVendor advisory
- 2026-09-22 17:56 UTCGHSA enrichment
- 2026-09-22 14:14 UTCVendor advisory
- 2026-09-22 14:14 UTCGHSA enrichment
- 2026-09-22 10:33 UTCVendor advisory
- 2026-09-22 10:32 UTCGHSA enrichment
- 2026-09-22 06:49 UTCVendor advisory
- 2026-09-22 06:49 UTCGHSA enrichment
- 2026-09-22 03:08 UTCVendor advisory
- 2026-09-22 03:08 UTCGHSA enrichment
- 2026-09-21 23:26 UTCEG score recompute
- 2026-09-21 23:26 UTCVendor advisory
- 2026-09-21 23:26 UTCGHSA enrichment
- 2026-09-21 19:45 UTCVendor advisory
- 2026-09-21 19:45 UTCGHSA enrichment
- 2026-09-21 19:09 UTCCISA KEV update
- 2026-09-21 16:03 UTCVendor advisory
- 2026-09-21 16:03 UTCGHSA enrichment
- 2026-09-21 12:21 UTCVendor advisory
- 2026-09-21 12:21 UTCGHSA enrichment
- 2026-09-21 08:39 UTCVendor advisory
- 2026-09-21 08:39 UTCGHSA enrichment
- 2026-09-21 04:57 UTCVendor advisory
- 2026-09-21 04:57 UTCGHSA enrichment
- 2026-09-21 01:16 UTCVendor advisory
- 2026-09-21 01:15 UTCGHSA enrichment
- 2026-09-20 21:32 UTCEG score recompute
- 2026-09-20 21:32 UTCVendor advisory
- 2026-09-20 21:32 UTCGHSA enrichment
- 2026-09-20 17:49 UTCVendor advisory
- 2026-09-20 17:49 UTCGHSA enrichment
- 2026-09-20 14:07 UTCVendor advisory
- 2026-09-20 14:07 UTCGHSA enrichment
- 2026-09-20 10:25 UTCVendor advisory
- 2026-09-20 10:25 UTCGHSA enrichment
- 2026-09-20 06:44 UTCVendor advisory
- 2026-09-20 06:43 UTCGHSA enrichment
- 2026-09-20 02:58 UTCVendor advisory
- 2026-09-20 02:58 UTCGHSA enrichment
- 2026-09-19 23:16 UTCVendor advisory
- 2026-09-19 23:16 UTCGHSA enrichment
- 2026-09-19 19:35 UTCVendor advisory
- 2026-09-19 19:35 UTCGHSA enrichment
- 2026-09-19 15:53 UTCEG score recompute
- 2026-09-19 15:53 UTCVendor advisory
- 2026-09-19 15:53 UTCGHSA enrichment
- 2026-09-19 12:10 UTCVendor advisory
- 2026-09-19 12:10 UTCGHSA enrichment
- 2026-09-19 08:27 UTCVendor advisory
- 2026-09-19 08:26 UTCGHSA enrichment
- 2026-09-19 04:44 UTCVendor advisory
- 2026-09-19 04:44 UTCGHSA enrichment
- 2026-09-19 01:02 UTCVendor advisory
- 2026-09-19 01:02 UTCGHSA enrichment
- 2026-09-18 21:20 UTCEG score recompute
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:8:chromium-browser
Same vendor
10 shownredhat:RHSA-2017:0499
Same CWE
10 shownCWE-125
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
See which npm, PyPI, Go, and Maven packages are affected by 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.