CVE-2020-16010

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Google Chrome for Android UI. For every flaw being used in attacks, see Exploited flaws; for Google’s, see Google flaws being used in attacks.

CVE-2020-16010 is a security flaw in Google Chrome for Android UI. Attackers can get past a security protection in Google Chrome for Android UI. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 3 Nov 2021.[1]

Google Chrome for Android UI is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Fixed in version 86.0.4240.185.

Description

CISA calls it a heap buffer overflow in Google Chrome for Android UI. In its words: “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.”[1]

The underlying weakness is out-of-bounds write (CWE-787), in MITRE’s list of common software weaknesses.[2]

It scores 9.6 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]

ProductFixed in
Chrome86.0.4240.185
chrome86.0.4240.185

Every device with Google Chrome for Android UI needs the update.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 3 Nov 2021, 365 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 3 May 2022 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 6%. That’s in the top 7% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Google has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Update Google Chrome for Android UI now.Install the latest update from Google on every device that has it, and restart when asked. Then turn on automatic updates, so the next fix arrives on its own.
  2. Check you’re on 86.0.4240.185 or later.Fixed in version 86.0.4240.185. Anything older is what attackers are going after.
  3. If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.6.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 6%.[4]

See also

Other Google flaws

  • CVE-2026-111497, Google Brotli: unchecked return value ·
  • CVE-2026-58704, Google Pixel: improper authorization ·
  • CVE-2026-87491, Chrome and other Chromium browsers: out of bounds write ·
  • CVE-2026-85046, Chrome and other Chromium browsers: type confusion ·
  • CVE-2026-11645, Chrome and other Chromium browsers: out-of-bounds read and write ·

Other out-of-bounds write flaws

Added the same day

  • CVE-2021-42258, BQE BillQuick Web Suite: SQL injection ·
  • CVE-2021-42013, Apache HTTP Server: path traversal ·
  • CVE-2021-41773, Apache HTTP Server: path traversal ·
  • CVE-2021-40539, Zoho ManageEngine: aDSelfService plus authentication bypass ·
  • CVE-2021-40444, Microsoft MSHTML: remote code execution ·

Every Google flaw on CISA’s list · Everything added in November 2021

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Google Chrome for Android UI Heap Buffer Overflow Vulnerability”. Known Exploited Vulnerabilities Catalog, added 3 Nov 2021.
  2. ^ National Institute of Standards and Technology. “CVE-2020-16010 Detail”. National Vulnerability Database, published 3 Nov 2020.
  3. ^ Google. Advisories and fixes: chromereleases.googleblog.com, crbug.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.064, percentile 93.7, 31 Oct 2026.
  5. CVE Program. “CVE-2020-16010”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.