Threats / Google / CVE-2020-16010
CVE-2020-16010
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chrome for Android UI vulnerability
Google Chrome for Android UI contains a heap buffer overflow (CWE-787) that allows a compromised renderer process to escape the sandbox via crafted HTML.
Verdict
Today item — known-exploited.
A remote attacker who has already compromised the renderer process can exploit this heap buffer overflow to break out of the sandbox, potentially gaining elevated privileges on the Android device. The vulnerability has been exploited in the wild.
CISA KEV Yes · 2021-11-034EPSS 0.06414 (verify live)5CVSS 9.6 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
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 2021-11-03).
Probability (EPSS)
EPSS 0.06414 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) · Affected: Google, Chrome for Android UI. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 365 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
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 designed to trigger a heap buffer overflow in Chrome's UI rendering layer.
Business
User visits attacker-controlled or compromised website, initiating the attack chain.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the buffer overflow to corrupt heap memory and escape the renderer sandbox.
Business
Attacker gains code execution outside the sandbox, bypassing Chrome's primary security boundary.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code with elevated privileges on the Android device.
Business
Device security is compromised; attacker can access user data, install malware, or pivot to other system components.
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