Threats / Google / CVE-2016-5198
CVE-2016-5198
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Out-of-bounds memory access in Chromium V8 allows remote code execution via crafted HTML, affecting Chrome, Edge, and Opera browsers.
Verdict
Today item — known-exploited.
A remote attacker can exploit memory safety flaws in V8 to read or write arbitrary memory and achieve code execution on a victim's system through a malicious webpage, with active exploitation observed 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.34703 — 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-125 Out-of-bounds Read, CWE-787 Out-of-bounds Write — 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 a malicious HTML page containing V8 bytecode or JavaScript that triggers an out-of-bounds memory access.
Business
Users visiting untrusted websites face immediate risk of system compromise without requiring user interaction beyond normal browsing.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the memory read/write primitives to bypass browser sandbox protections and gain code execution in the renderer process.
Business
Browser security isolation mechanisms fail, allowing attackers to escape the sandbox and potentially access system resources.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code with the privileges of the browser process to install malware, steal credentials, or pivot to the host system.
Business
Affected users experience data theft, credential compromise, or full system infection, damaging trust in browser security and organizational security posture.
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