Threats / Google / CVE-2018-6065
CVE-2018-6065
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Integer overflow in Chromium V8 engine allows remote code execution via crafted HTML, affecting Chrome, Edge, and Opera browsers.
Verdict
Today item — known-exploited.
A remote attacker can trigger heap corruption through a malicious webpage, potentially achieving arbitrary code execution in the context of the affected browser with high exploitability.
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
5 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.58822 — 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-190 Integer Overflow, 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 a malicious HTML page that triggers integer overflow in V8 JavaScript engine
Business
User visits attacker-controlled or compromised website without additional user interaction required
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Exploit heap corruption to overwrite adjacent memory and gain code execution
Business
Attacker executes arbitrary code with browser process privileges, accessing user data and system resources
3
Lateral reach — past segmentation narrative 3
Attacker
Establish persistence or pivot to system compromise
Business
Confidentiality, integrity, and availability of user systems compromised; potential lateral movement to network
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