Threats / Google / CVE-2016-1646
CVE-2016-1646
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 contains an out-of-bounds read vulnerability allowing remote attackers to cause denial of service or unspecified impact via crafted JavaScript code.
Verdict
Today item — known-exploited.
Out-of-bounds read in V8 engine permits remote code execution or denial of service through malicious JavaScript. Affects Chrome, Edge, Opera and other Chromium-based browsers. Actively exploited in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-06-08).
Probability (EPSS)
EPSS 0.45298 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium V8. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious JavaScript that triggers an out-of-bounds memory read in the V8 engine.
Business
User visits attacker-controlled or compromised website and browser crashes or becomes unstable.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the memory read to leak sensitive data from the browser process or escalate to code execution.
Business
Confidential user data, credentials, or session tokens are exposed or attacker gains arbitrary code execution.
3
Lateral reach — past segmentation narrative 3
Attacker
I distribute the exploit through watering hole attacks or drive-by downloads targeting Chromium users.
Business
Large user populations across Chrome, Edge, and Opera face simultaneous compromise risk.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05