CVE-2020-16010
KEVGoogle Chrome for Android UI Heap Buffer Overflow Vulnerability
Description
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.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HPublishedNov 3, 2020
Last modifiedJun 17, 2026
Added to KEVNov 3, 2021
Remediation dueMay 3, 2022
References
- chromereleases.googleblog.com/2020/11/chrome-for-android-update.htmlVendor Advisory
- crbug.com/1144368Issue TrackingVendor Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-16010US Government Resource
0 recent articles mention this CVE
79
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1638 days
- CVSS
- 9.6 CRITICAL
- EPSS (30-day exploit probability)
- 6.4% · top 6% of all CVEs
- Weakness
- CWE-787
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.