Threats / Google / CVE-2018-17480
CVE-2018-17480
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Out-of-bounds write in Chromium V8 allows remote code execution within sandbox via crafted HTML, affecting Chrome, Edge, and other V8-based browsers.
Verdict
Today item — known-exploited.
Remote attacker delivers malicious HTML to execute arbitrary code in browser sandbox. Exploitation observed in wild. Out-of-bounds write enables memory corruption and code execution despite sandbox constraints.
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.34292 — 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-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
Craft HTML page triggering out-of-bounds write in V8 JavaScript engine
Business
User visits attacker-controlled or compromised website
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Corrupt V8 memory structures to gain code execution within browser sandbox
Business
Malicious code executes with browser process privileges
3
Lateral reach — past segmentation narrative 3
Attacker
Escape sandbox or access sensitive data available to browser context
Business
Credentials, session tokens, or user data exfiltrated from browser memory
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