Threats / Google / CVE-2018-17463
CVE-2018-17463
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Google Chromium V8 contains an unspecified vulnerability allowing remote code execution within a sandbox via crafted HTML. Affects Chrome, Edge, Opera, and other Chromium-based browsers.
Verdict
Today item — known-exploited.
Remote attacker can execute arbitrary code in the V8 sandbox by delivering a malicious HTML page to a victim. High exploitability in the wild with EPSS 0.92 indicates active weaponization and widespread attack potential across multiple browser vendors.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported 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.83898 — 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.
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 engine exploit code.
Business
Attacker gains arbitrary code execution within browser sandbox, enabling data theft, credential harvesting, or lateral movement to host system.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I distribute the HTML via phishing, watering hole, or ad network to reach target users.
Business
Widespread browser compromise across Chrome, Edge, Opera user bases creates mass infection vector for malware deployment.
3
Lateral reach — past segmentation narrative 3
Attacker
I escape or bypass the sandbox to access host system resources and user data.
Business
Sandbox containment failure exposes operating system, file systems, and sensitive user information to compromise.
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