Secuno
ENNL
Book demo

CVE-2020-16010

Google Chrome for Android UI Heap Buffer Overflow

9.6 CRITICALActively exploited (CISA KEV)EPSS 6.36%
  1. Published3 Nov 2020
  2. Added to CISA KEV3 Nov 2021
  3. Remediation due3 May 2022
Actively exploited (CISA KEV)

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.

Added to KEV: 3 Nov 2021Federal remediation due: 3 May 2022

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

Google Chrome< 86.0.4240.185

Remediation

Fixed in
Google Chrome≥ 86.0.4240.185

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1078158.5
MariaDB server is a community developed fork of MySQL server. From 10.6.1 until…
CVE-2026-195708.8
The LE Audio Broadcast Sink in subsys/bluetooth/audio/bap_broadcast_sink.c copies…
CVE-2026-1079099.1
A heap-based out-of-bounds write in the ws_read_frame function (src/bolt/ws.c) and the…
CVE-2026-1079089.8
A heap-based out-of-bounds write in the BoltReadHandler function (src/bolt/bolt_api.c)…
CVE-2026-823448.1
IBM Guardium Data Protection 12.0, 12.1 is vulnerable to a heap-based buffer overflow…
CVE-2026-823358.1
IBM Guardium Data Protection 12.0, 12.1, 12.2 is vulnerable to a heap-based buffer…

Frequently asked

Is CVE-2020-16010 being actively exploited?

Yes. CVE-2020-16010 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Nov 2021.

How severe is CVE-2020-16010?

CVE-2020-16010 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 6.36% probability of exploitation.

Which products are affected by CVE-2020-16010?

Affected products include Google Chrome.

How do I fix CVE-2020-16010?

Upgrade affected software to a fixed version, for example Google Chrome 86.0.4240.185 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2020-16010 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.