CVE-2020-16010 Google Chrome for Android UI Heap Buffer Overflow

Exploited in the wild Critical 9.6 Published 3 Nov 2020 Updated 12 Jan 2026

A heap buffer overflow in Chrome's UI allows a compromised renderer to escape the sandbox and execute arbitrary code via a crafted HTML page.

Exploited in the wild: Since 3 Nov 2021
Login needed: Not needed
Attackable: Over the internet
Victim action needed: A user has to click or open something
Fix: None listed

What is CVE-2020-16010?

CVE-2020-16010 is a critical memory corruption vulnerability in Google Chrome, published on 3 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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.

Weakness: CWE-787, CWE-122

Which versions are affected by CVE-2020-16010?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2020-16010?

No fix has been published for CVE-2020-16010 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2020-16010 being exploited?

Yes. Attackers have exploited CVE-2020-16010 in the wild since at least 3 Nov 2021.

All Google Chrome vulnerabilities

Sources

Also known as GHSA-x9cj-gxph-5cgf.