CVE-2020-16017
Google Chrome Use-After-Free
- Published8 Jan 2021
- Added to CISA KEV3 Nov 2021
- Remediation due3 May 2022
Description
Use after free in site isolation in Google Chrome prior to 86.0.4240.198 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
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2020-16017 being actively exploited?
Yes. CVE-2020-16017 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 3 Nov 2021.
How severe is CVE-2020-16017?
CVE-2020-16017 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 2.73% probability of exploitation.
Which products are affected by CVE-2020-16017?
Affected products include Google Chrome.
How do I fix CVE-2020-16017?
Upgrade affected software to a fixed version, for example Google Chrome 86.0.4240.198 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2020-16017 against the real software inventory on every managed device, every day. 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, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.