Threats / Google / CVE-2020-6418
CVE-2020-6418
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Google Chromium V8 vulnerability
Type confusion vulnerability in Chromium V8 allows remote attackers to exploit heap corruption through crafted HTML, affecting Chrome, Edge, and Opera browsers.
Verdict
Today item — known-exploited.
A type confusion flaw in V8 enables heap corruption exploitation via malicious web content. The high EPSS score and confirmed wild exploitation indicate active abuse against browser users across multiple Chromium-based products.
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
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 2021-11-03).
Probability (EPSS)
EPSS 0.78808 — 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 untrusted websites face arbitrary code execution within their browser process.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the resulting heap corruption to achieve code execution in the browser context.
Business
Attackers gain ability to steal credentials, session tokens, and sensitive data from compromised user sessions.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage browser execution to install malware or establish persistence on the victim's system.
Business
Organizations experience data breaches, system compromise, and potential lateral movement into corporate networks.
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