CVE-2017-5030

Google Chromium V8 Memory Corruption Vulnerability

  • High 8.8
  • Exploited: added to CISA KEV 8 Jun 2022

Description

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.

Key facts

Published
24 Apr 2017
Last changed
21 Oct 2025
Assigned by
Chrome
KEV added
8 Jun 2022
KEV fix due
22 Jun 2022
EPSS
40.635% likely to be exploited in the next 30 days, higher than 98.674% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: active; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.8CVSS 3.1, Highfrom CISA (ADP container)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

What to do

  • Apply updates per vendor instructions.CISA KEV required action

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
n/aGoogle Chrome prior to 57.0.2987.98 for Linux, Windows and Mac, and 57.0.2987.108 for Android
  • Google Chrome prior to 57.0.2987.98 for Linux, Windows and Mac, and 57.0.2987.108 for Android (affected)

Timeline

  1. 24 Apr 2017 Published
  2. 8 Jun 2022 CVE-2017-5030 added to CISA KEV
  3. 8 Jun 2022 Added to the CISA KEV catalogue

Weakness

References