basicsecurity.net
Proof, not just disclosure.
Threats / Google / CVE-2020-16013
CVE-2020-16013 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Google Chromium V8 vulnerability

Google Chromium V8 contains a heap corruption vulnerability allowing remote attackers to exploit browsers via crafted HTML pages. Affects Chrome, Edge, Opera and other Chromium-based browsers.

Verdict

Today item — known-exploited.

Out-of-bounds write in V8 engine enables remote code execution through malicious web content. Exploitation observed in the wild. Impacts confidentiality, integrity, and availability of affected browser users.

CISA KEV Yes · 2021-11-033EPSS 0.02826 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
2 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.02826 — 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.
NVD ↗Reported
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.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
Craft a malicious HTML page that triggers heap corruption in the V8 JavaScript engine
Business
User browsing the web encounters compromised site and browser process is exploited
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Achieve arbitrary code execution within the browser's renderer process context
Business
Attacker gains ability to steal user data, install malware, or pivot to system compromise
3

Lateral reach — past segmentation narrative 3

Attacker
Exfiltrate sensitive information or establish persistence on the victim's machine
Business
Organization faces data breach, credential theft, or endpoint compromise across user base
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 2 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Chrome (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ChromeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.