How severe is CVE-2017-5030?

CVE-2017-5030 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-5030?

Affected package information for CVE-2017-5030 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2017-5030?

No fixed version has been published for CVE-2017-5030 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2017-5030 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2017-5030, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-5030?

CVE-2017-5030 has an EPSS (Exploit Prediction Scoring System) score of 50.3%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2017-5030 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-5030 (Google Chromium V8 Memory Corruption Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-06-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-22. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-5030?

CVE-2017-5030 is classified as Out-of-bounds Read (CWE-125). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2017-5030?

CVE-2017-5030 affects debian debian linux (2 versions, e.g. 8.0, 9.0); google chrome; redhat enterprise linux desktop (1 version, e.g. 6.0); redhat enterprise linux server (1 version, e.g. 6.0), and 1 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2017-5030 published, and has it been updated?

CVE-2017-5030 was published on April 24, 2017 and was last updated on April 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-06-08 — agencies required to remediate by 2022-06-22

CVE-2017-5030

HIGH

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…

Published

Apr 24, 2017

Updated

Apr 21, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

50.3%probability of exploitation in next 30 days

High Risk98th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

5 products · 7 configurations

debian linuxdebian

2 versions

8.09.0

Application

chromegoogle

< 57.0.2987.108

range

enterprise linux desktopredhat

1 version

6.0

enterprise linux serverredhat

1 version

6.0

enterprise linux workstationredhat

1 version

6.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Incorrect handling of complex species in V8 in Google Chrome prior to 57…

github.comAwesomePocJun 2020

Incorrect handling of complex species in V8 in Google Chrome prior to 57…

cisa.govCISAJun 2022

Incorrect handling of complex species in V8 in Google Chrome prior to 57…

trendmicro.comAPIMar 2020

Incorrect handling of complex species in V8 in Google Chrome prior to 57…

crbug.comNVDJun 2024

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-5030 in your stack?

O3 detects CVE-2017-5030 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

8.8/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

Required

S:Scope

Unchanged

C:Confidentiality

High

I:Integrity

High

A:Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-125Out-of-bounds Read

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Apr 24, 2017

First exploit

Jun 26, 2020

KEV added

Jun 8, 2022

Last updated

Apr 21, 2026

Identifiers

CVE-2017-5030

References

Advisoryrhn.redhat.com Advisorydebian.org Advisorysecurityfocus.com Advisorychromereleases.googleblog.com Advisorysecurity.gentoo.org Advisoryzerodayinitiative.com Advisoryrhn.redhat.com Advisorydebian.org Advisorysecurityfocus.com Advisorychromereleases.googleblog.com Advisorysecurity.gentoo.org Advisoryzerodayinitiative.com Exploit / PoCcrbug.com Exploit / PoCcrbug.com Webcisa.gov

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.