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
CVE-2020-16010 explained
CVE-2020-16010 is a heap buffer overflow in the UI component of Google Chrome on Android before 86.0.4240.185. An attacker who has already compromised the renderer process could use a crafted HTML page to potentially escape the browser sandbox. CISA lists it as known to be exploited, so unpatched devices face real risk.
Impact
A remote attacker who already controls the renderer process could break out of Chrome's sandbox and gain wider access on the device. The victim must open a crafted HTML page. Exploitation needs no privileges and has low complexity. CISA rates the technical impact as total but considers it not automatable. Confidentiality, integrity and availability impacts are all high, and the scope is changed.
Who is affected
Google Chrome on Android versions before 86.0.4240.185 are affected, according to the CVE record published by the Chrome CNA. Version 86.0.4240.185 contains the fix.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
What to do
- Update Google Chrome on all Android devices to
86.0.4240.185or later. - Use mobile device management or app store policies to enforce automatic Chrome updates.
- Verify the installed Chrome version on managed Android devices and flag outdated installations.
- Follow the vendor advisory and CISA's required action to apply updates per vendor instructions.
Written with AI from the data on this page and checked against it automatically.
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
Questions about CVE-2020-16010
- Is CVE-2020-16010 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03. Whether it has been used in ransomware campaigns is unknown.
- Which version fixes the vulnerability?
- Google Chrome on Android
86.0.4240.185contains the fix. All earlier versions are affected. - Can an attacker exploit this on its own?
- Not directly. The attacker must first have compromised the renderer process, and the user must open a crafted HTML page. The flaw then could allow a sandbox escape.
Written with AI from the data on this page and checked against it automatically.
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-22. Always confirm with the vendor's or distribution's advisory before patching.