CVE-2020-16010: Google Chrome for Android UI Heap Buffer Overflow
Google Chrome for Android UI · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CISA ADP)
- 9.6
- critical
- EPSS (exploit probability, 30 days)
- 6.4%
- higher than 93.8% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Automatable (CISA SSVC)
- no
- technical impact: total
What is CVE-2020-16010?
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 86.0.4240.185
- 86.0.4240.185
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
How to fix it
- Update to a fixed version: 86.0.4240.185.
- Vendor advisory: chromereleases.googleblog.com/2020/11/chrome-for-android-…
- CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-122 Heap-based Buffer Overflow
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.