How severe is CVE-2017-5070?

CVE-2017-5070 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-5070 being actively exploited?

Yes. CVE-2017-5070 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2022-06-08, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2017-5070?

CVE-2017-5070 primarily affects Google Chrome. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-5070?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2017-5070 have an EU (EUVD) identifier?

Yes. CVE-2017-5070 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2017-14179. It is also flagged as exploited in the EUVD (since 2022-06-08).

When was CVE-2017-5070 published?

CVE-2017-5070 was published on 2017-10-27 and last updated on 2026-06-17.

CVE-2017-5070

CVE-2017-5070 is a high-severity vulnerability in Google Chrome with a CVSS 3.x base score of 8.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2022-06-08). The underlying weakness is classified as CWE-843.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.8
EPSS exploit prediction: 31% (98th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2022-06-08)
EU (EUVD) id: EUVD-2017-14179
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2022-06-08)
Weakness: CWE-843
Affected product: Google Chrome
Published: 2017-10-27
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2017-5070?: 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.
How severe is CVE-2017-5070?: CVE-2017-5070 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-5070 being actively exploited?: Yes. CVE-2017-5070 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2022-06-08, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2017-5070?: CVE-2017-5070 primarily affects Google Chrome. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-5070?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2017-5070 have an EU (EUVD) identifier?: Yes. CVE-2017-5070 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2017-14179. It is also flagged as exploited in the EUVD (since 2022-06-08).
When was CVE-2017-5070 published?: CVE-2017-5070 was published on 2017-10-27 and last updated on 2026-06-17.

References

Affected products (4)

cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
cpe:2.3:o:redhat:enterprise_linux_desktop:6.0:*:*:*:*:*:*:*
cpe:2.3:o:redhat:enterprise_linux_server:6.0:*:*:*:*:*:*:*
cpe:2.3:o:redhat:enterprise_linux_workstation:6.0:*:*:*:*:*:*:*

More vulnerabilities in Google Chrome

CVE-2026-13782 — Critical (CVSS 10.0): Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
CVE-2015-8548 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google V8 before 4.7.80.23, as used in Google Chrome before 47.0.2526.80, allow…
CVE-2015-6791 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.80 allow attackers to cause a denial of service…
CVE-2015-6788 — Critical (CVSS 10.0): The ObjectBackedNativeHandler class in extensions/renderer/object_backed_native_handler.cc in the extensions subsystem…
CVE-2015-8480 — Critical (CVSS 10.0): The VideoFramePool::PoolImpl::CreateFrame function in media/base/video_frame_pool.cc in Google Chrome before…
CVE-2015-6787 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.73 allow attackers to cause a denial of service…

All CVEs affecting Google Chrome →

Other CWE-843 vulnerabilities

CVE-2021-33970 — Critical (CVSS 10.0): Buffer Overflow vulnerability in Qihoo 360 Chrome v13.0.2170.0 allows attacker to escalate priveleges.
CVE-2010-2299 — Critical (CVSS 10.0): The Clipboard::DispatchObject function in app/clipboard/clipboard.cc in Google Chrome before 5.0.375.70 does not…
CVE-2023-22579 — Critical (CVSS 9.9): Due to improper parameter filtering in the sequalize js library, can a attacker peform injection.
CVE-2026-13776 — Critical (CVSS 9.8): Type Confusion in Dawn in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
CVE-2026-43038 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: ipv6: icmp: clear skb2->cb[] in…
CVE-2025-70023 — Critical (CVSS 9.8): An issue pertaining to CWE-843: Access of Resource Using Incompatible Type was discovered in transloadit uppy v0.25.6.

Browse all CWE-843 vulnerabilities →