How severe is CVE-2016-1646?

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

Which packages are affected by CVE-2016-1646?

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

How do I fix CVE-2016-1646?

No fixed version has been published for CVE-2016-1646 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-2016-1646 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2016-1646, 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-2016-1646?

CVE-2016-1646 has an EPSS (Exploit Prediction Scoring System) score of 66.9%, placing it in the 99th 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-2016-1646 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2016-1646 (Google Chromium V8 Out-of-Bounds Read 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-2016-1646?

CVE-2016-1646 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-2016-1646?

CVE-2016-1646 affects canonical ubuntu linux (3 versions, e.g. 14.04, 15.10, 16.04); debian debian linux (2 versions, e.g. 8.0, 9.0); google chrome; opensuse leap (1 version, e.g. 42.1), and 6 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2016-1646 published, and has it been updated?

CVE-2016-1646 was published on March 29, 2016 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-2016-1646

HIGH

The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, does not properly consider element data types, which allows remote…

Published

Mar 29, 2016

Updated

Apr 21, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

66.9%probability of exploitation in next 30 days

High Risk99th 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

The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, does not properly consider element data types, which allows remote attackers to cause a denial of service (out-of-bounds read) or possibly have unspecified other impact via crafted JavaScript code.

Affected Products

10 products · 13 configurations

ubuntu linuxcanonical

3 versions

14.0415.1016.04

debian linuxdebian

2 versions

8.09.0

Application

chromegoogle

< 49.0.2623.108

range

leapopensuse

1 version

42.1

opensuseopensuse

1 version

13.1

enterprise linux desktopredhat

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.

The Array.prototype.concat implementation in builtins.cc in Google V8, a…

github.comAwesomePocJun 2020

The Array.prototype.concat implementation in builtins.cc in Google V8, a…

cisa.govCISAJun 2022

The Array.prototype.concat implementation in builtins.cc in Google V8, a…

trendmicro.comAPIMar 2020

The Array.prototype.concat implementation in builtins.cc in Google V8, a…

code.google.comNVDJun 2024

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-1646 in your stack?

O3 detects CVE-2016-1646 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