Skip to content
skopnix

CVE-2016-1646 · Published 29 Mar 2016

Google Chromium V8

On CISA's KEV list 2262 days after disclosure; 1 attacker cited in reports.

Google Chromium V8 Engine contains an out-of-bounds read vulnerability that allows a remote attacker to cause a denial of service or possibly have another unspecified impact via crafted JavaScript code. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

CISA required action (federal due date 22 Jun 2022): Apply updates per vendor instructions.

Signals

KEV, exploited in the wild
yes, added 8 Jun 2022, due 22 Jun 2022
EPSS, 30-day forecast
48%, 99th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 29 Mar 2016 to today

2,262 days from disclosure to the KEV listing
2018201920202021202420252026Disclosed 29 Mar 2016KEV 8 Jun 2022today
  1. Disclosed
  2. KEV+2262 d

2,262 days from disclosure to the KEV listing

Who exploits it 1 citation

  1. POISON CARP
    1. “Other exploits include what appears to be lightly modified versions of Chrome exploit code published on the personal GitHub pages of a member of Tencent’s Xuanwu Lab ( CVE-2016-1646 ), a member of Qihoo 360’s Vulcan Team ( CVE-2018-17480 ), and by a Google Project Zero member on the Chrome Bug Tracker ( CVE-2018-6065 ).”

      cited as exploiting · named nearby · citizenlab.ca ↗ · 17 Oct 2026

Each actor is cited by the quoted source, linked under the quote. A citation is that source's claim, not our confirmation.

Linked 1 in our graph

Exploited by

  1. actorPOISON CARP

Links our graph holds for this CVE, strongest first. The same data is in the graph API.

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 0 dispatches

No dispatch on our wire has named this CVE yet.

Public exploit code none in our sources

No public exploit in the sources we track: GitHub proof-of-concept lists, Metasploit and Exploit-DB. Absence is not proof that none exists.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check