CVE-2016-1646

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 48%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
9.0(high)
EPSS
98.7%
KEV
⚠ Exploited

Published

March 29, 2016

Last Modified

April 21, 2026

Advisory Details (4)

Auto-updated May 2, 2026
No patch confirmed yet.
generic

Issue 1804963002: [builtins] Fix Array.prototype.concat bug - Code Review

https://codereview.chromium.org/1804963002/
generic
https://code.google.com/p/chromium/issues/detail?id=594574
generic
http://rhn.redhat.com/errata/RHSA-2016-0525.html
generic

Chrome Releases: Stable Channel Update

http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuoxideqt-codecs-extra (1.14.7-0ubuntu1) @ xenial2026-07-21ubuntu
redhatchromium-browser-0:49.0.2623.108-1.el62016-03-30redhat

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.

Weakness Classification(2)

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 103× in last 7d / 427× 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 782 total refreshes for this CVE.

  1. 2026-07-22 16:51 UTCEG score recompute
  2. 2026-07-22 16:51 UTCVendor advisory
  3. 2026-07-22 16:51 UTCGHSA enrichment
  4. 2026-07-22 14:04 UTCEPSS rescore
  5. 2026-07-22 13:00 UTCVendor advisory
  6. 2026-07-22 13:00 UTCGHSA enrichment
  7. 2026-07-22 09:11 UTCVendor advisory
  8. 2026-07-22 09:11 UTCGHSA enrichment
  9. 2026-07-22 05:23 UTCVendor advisory
  10. 2026-07-22 05:22 UTCGHSA enrichment
  11. 2026-07-22 01:09 UTCVendor advisory
  12. 2026-07-22 01:09 UTCGHSA enrichment
  13. 2026-07-21 18:31 UTCEG score recompute
  14. 2026-07-21 18:31 UTCVendor advisory
  15. 2026-07-21 18:30 UTCGHSA enrichment
  16. 2026-07-21 15:21 UTCEPSS rescore
  17. 2026-07-21 15:21 UTCEPSS rescore
  18. 2026-07-21 14:40 UTCVendor advisory
  19. 2026-07-21 14:40 UTCGHSA enrichment
  20. 2026-07-21 14:37 UTCCISA KEV update
  21. 2026-07-21 10:50 UTCVendor advisory
  22. 2026-07-21 10:49 UTCGHSA enrichment
  23. 2026-07-21 06:58 UTCVendor advisory
  24. 2026-07-21 06:58 UTCGHSA enrichment
  25. 2026-07-21 03:10 UTCVendor advisory
Show 75 more
  1. 2026-07-21 03:10 UTCGHSA enrichment
  2. 2026-07-20 23:21 UTCVendor advisory
  3. 2026-07-20 23:21 UTCGHSA enrichment
  4. 2026-07-20 19:32 UTCEG score recompute
  5. 2026-07-20 19:32 UTCVendor advisory
  6. 2026-07-20 19:32 UTCGHSA enrichment
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-20 15:44 UTCVendor advisory
  9. 2026-07-20 15:44 UTCGHSA enrichment
  10. 2026-07-20 11:55 UTCVendor advisory
  11. 2026-07-20 11:55 UTCGHSA enrichment
  12. 2026-07-20 08:06 UTCVendor advisory
  13. 2026-07-20 08:06 UTCGHSA enrichment
  14. 2026-07-20 04:15 UTCVendor advisory
  15. 2026-07-20 04:15 UTCGHSA enrichment
  16. 2026-07-20 00:26 UTCVendor advisory
  17. 2026-07-19 20:37 UTCVendor advisory
  18. 2026-07-19 20:37 UTCGHSA enrichment
  19. 2026-07-19 16:48 UTCVendor advisory
  20. 2026-07-19 16:48 UTCGHSA enrichment
  21. 2026-07-19 12:59 UTCVendor advisory
  22. 2026-07-19 12:59 UTCGHSA enrichment
  23. 2026-07-19 09:11 UTCVendor advisory
  24. 2026-07-19 09:11 UTCGHSA enrichment
  25. 2026-07-19 05:22 UTCEG score recompute
  26. 2026-07-19 05:22 UTCVendor advisory
  27. 2026-07-19 05:22 UTCGHSA enrichment
  28. 2026-07-19 02:26 UTCEPSS rescore
  29. 2026-07-19 02:26 UTCEPSS rescore
  30. 2026-07-19 01:32 UTCVendor advisory
  31. 2026-07-19 01:32 UTCGHSA enrichment
  32. 2026-07-18 21:43 UTCVendor advisory
  33. 2026-07-18 21:43 UTCGHSA enrichment
  34. 2026-07-18 17:55 UTCVendor advisory
  35. 2026-07-18 17:55 UTCGHSA enrichment
  36. 2026-07-18 14:06 UTCVendor advisory
  37. 2026-07-18 14:06 UTCGHSA enrichment
  38. 2026-07-18 10:17 UTCEG score recompute
  39. 2026-07-18 10:17 UTCVendor advisory
  40. 2026-07-18 10:16 UTCGHSA enrichment
  41. 2026-07-18 10:00 UTCEPSS rescore
  42. 2026-07-18 10:00 UTCEPSS rescore
  43. 2026-07-18 06:28 UTCVendor advisory
  44. 2026-07-18 06:28 UTCGHSA enrichment
  45. 2026-07-18 02:39 UTCVendor advisory
  46. 2026-07-18 02:39 UTCGHSA enrichment
  47. 2026-07-17 22:50 UTCVendor advisory
  48. 2026-07-17 22:50 UTCGHSA enrichment
  49. 2026-07-17 19:01 UTCVendor advisory
  50. 2026-07-17 19:01 UTCGHSA enrichment
  51. 2026-07-17 15:12 UTCVendor advisory
  52. 2026-07-17 15:12 UTCGHSA enrichment
  53. 2026-07-17 11:23 UTCVendor advisory
  54. 2026-07-17 11:23 UTCGHSA enrichment
  55. 2026-07-17 07:33 UTCEG score recompute
  56. 2026-07-17 07:33 UTCVendor advisory
  57. 2026-07-17 07:33 UTCGHSA enrichment
  58. 2026-07-17 03:44 UTCVendor advisory
  59. 2026-07-17 03:44 UTCGHSA enrichment
  60. 2026-07-16 23:55 UTCVendor advisory
  61. 2026-07-16 23:55 UTCGHSA enrichment
  62. 2026-07-16 20:07 UTCVendor advisory
  63. 2026-07-16 20:07 UTCGHSA enrichment
  64. 2026-07-16 17:04 UTCCISA KEV update
  65. 2026-07-16 16:59 UTCEPSS rescore
  66. 2026-07-16 16:59 UTCEPSS rescore
  67. 2026-07-16 16:18 UTCVendor advisory
  68. 2026-07-16 16:18 UTCGHSA enrichment
  69. 2026-07-16 12:28 UTCVendor advisory
  70. 2026-07-16 12:28 UTCGHSA enrichment
  71. 2026-07-16 08:39 UTCVendor advisory
  72. 2026-07-16 08:39 UTCGHSA enrichment
  73. 2026-07-16 04:50 UTCVendor advisory
  74. 2026-07-16 04:50 UTCGHSA enrichment
  75. 2026-07-16 01:02 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2016-1646?
CVE-2016-1646 is a high vulnerability published on March 29, 2016. 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…
When was CVE-2016-1646 disclosed?
CVE-2016-1646 was first published in the National Vulnerability Database on March 29, 2016, with the most recent update on April 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-1646 actively exploited?
Yes. CISA added CVE-2016-1646 to the Known Exploited Vulnerabilities catalog on June 8, 2022, affecting Google Chromium V8. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2016-1646?
CVE-2016-1646 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2016-1646?
CVE-2016-1646 affects Google Chromium V8. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2016-1646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-1646, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-1646

Explore →

Is Your Infrastructure Affected by CVE-2016-1646?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs