CVE-2020-16010

Known Exploited

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.

Category

8.8
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 21.06% Top 5%
KEV Since 
Vendor Advisory googleblog.com Vendor Advisory crbug.com
Affected: Google Chrome
Published at:
Updated at:

References

Link Tags
https://crbug.com/1144368 permissions required vendor advisory
https://chromereleases.googleblog.com/2020/11/chrome-for-android-update.html vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-16010?
CVE-2020-16010 has been scored as a high severity vulnerability.
How to fix CVE-2020-16010?
To fix CVE-2020-16010, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-16010 being actively exploited in the wild?
It is confirmed that CVE-2020-16010 is actively exploited. Be extra cautious if you are using vulnerable components. According to its EPSS score, there is a ~21% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-16010?
CVE-2020-16010 affects Google Chrome.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.