Skip to content
Sign in
CVE-2020-160109.6CriticalCWE-122

CVE-2020-16010: Google Chrome vulnerability

Google · Chrome

Vendor fix available · Affected: Google Chrome · Exploitation: in CISA KEV since 3 Nov 2021

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

ExploitationIn CISA KEV

  1. In CISA KEVCISA KEV catalogue3 Nov 2021
  2. Exploited (reported): not seen
  3. Scanning observed: not seen
  4. Proof of concept public: not seen
  5. Not established: not seen
6.4%probability of exploitation in the next 30 days
93rd percentile
050100

Higher than 93% of scored CVEs

9.6CriticalCVSS 3.1
LowCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • Google · Chromebefore 86.0.4240.185

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Exploited in the wild. Listed in the CISA Known Exploited Vulnerabilities catalogue.
CISA KEV
Listed since 3 Nov 2021 · catalogue entry
Public check
No public nuclei template
Vendor
Google
Published
November 2020

What changed

  1. CISA added it to the KEV catalogue CISA

CoverageNo articles yet

No CyberSIXT article names CVE-2020-16010 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in