Threats / Google / CVE-2017-5070
CVE-2017-5070
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Type confusion vulnerability in Chromium V8 allows remote code execution within sandbox via crafted HTML, affecting Chrome, Edge, and Opera browsers.
Verdict
Today item — known-exploited.
A type confusion flaw in V8 enables attackers to execute arbitrary code in the browser sandbox through malicious web content. High exploitability in the wild with significant attack surface across multiple browser implementations.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 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.31212 — 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-843 Type Confusion — 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 that triggers type confusion in the V8 JavaScript engine.
Business
Users visiting attacker-controlled or compromised websites face arbitrary code execution risk within browser sandbox.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the type confusion to break out of or escalate privileges within the V8 sandbox environment.
Business
Successful sandbox escape could lead to system compromise, data theft, or malware installation on affected user machines.
3
Lateral reach — past segmentation narrative 3
Attacker
I distribute the exploit through drive-by downloads or watering hole attacks targeting browser users.
Business
Organizations face increased incident response costs and potential data breach liability from widespread browser-based attacks.
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