CVE-2020-16010
CRITICALCISA KEVEPSS 93th pctlDescription
Heap buffer overflow in UI in Google Chrome on Android prior to 86.0.4240.185 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Exploit Intelligence
High risk: more likely to be exploited than 93% of all known CVEs.
Google Chrome for Android UI Heap Buffer Overflow Vulnerability
Google Chrome for Android UI contains a heap buffer overflow vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.
Apply updates per vendor instructions.
Remediation due: 2022-05-03
References
Related Vulnerabilities
Other CWE-787 (Out-of-bounds Write) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-22457 | Critical | 9.0 | 100% | KEV + Ransom | Fix |
| CVE-2025-0282 | Critical | 9.0 | 100% | KEV + Ransom | - |
| CVE-2015-3113 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2021-20038 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2023-4863 | High | 8.8 | 100% | KEV | Fix |
| CVE-2020-16040 | Medium | 6.5 | 100% | - | Fix |
Common questions
How do I fix CVE-2020-16010?
Published advisories record a fix for 7 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2020-16010 being actively exploited?
Yes. CVE-2020-16010 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. US federal agencies were required to remediate it by 2022-05-03. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2020-16010?
CVE-2020-16010 has a CVSS v3 base score of 9.6, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2020-16010 affect?
Published advisories record a fix for Google Chrome (Windows application), Google Chrome (EXE) (Windows application), Google Chrome Beta (Windows application), Google Chrome Beta (EXE) (Windows application), and 3 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2020-16010
Markdown
[](https://tridentstack.com/cve/CVE-2020-16010)HTML
<a href="https://tridentstack.com/cve/CVE-2020-16010"><img src="https://tridentstack.com/cve/badge/CVE-2020-16010.svg" alt="CVE-2020-16010"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-01-14.