CVE-2020-16017: Google Chrome Use-After-Free
Google Chrome · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.
- CVSS v3.1 (CVE record)
- 9.6
- critical
- EPSS (exploit probability, 30 days)
- 2.7%
- higher than 86.4% of all CVEs
- Added to CISA KEV
- 2021-11-03
- US federal due date 2022-05-03
- Ubuntu priority
- medium
CVE-2020-16017 explained
CVE-2020-16017 is a use-after-free flaw in the site isolation feature of Google Chrome before 86.0.4240.198. An attacker who has already compromised the renderer process could use a crafted HTML page to potentially escape the browser sandbox. It is listed in CISA's Known Exploited Vulnerabilities catalog, so prompt patching matters.
Impact
A remote attacker who has already compromised the renderer process may escape the sandbox through a crafted HTML page. No privileges are needed, but a user must interact, for example by visiting the page. The scope is changed, so a successful attack can reach beyond the browser sandbox. Confidentiality, integrity and availability impacts are all high. CISA lists the flaw as known exploited. Whether it has been used by ransomware is unknown.
Who is affected
The chromium-browser source package is affected on two Ubuntu releases. Both have fixed versions in the standard archive. Ubuntu 16.04 LTS is fixed in 86.0.4240.198-0ubuntu0.16.04.1, but this release is end of life. Ubuntu 18.04 LTS is fixed in 86.0.4240.198-0ubuntu0.18.04.1. Standard support for 18.04 has ended, and further fixes there require Ubuntu Pro (ESM). Upstream, Google Chrome versions before 86.0.4240.198 are affected.
Written with AI from the data on this page and checked against it automatically.
Official 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.
CISA required action: Apply updates per vendor instructions.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 86.0.4240.198
- 86.0.4240.198
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 18.04 LTS·chromium-browser
Fixed: 86.0.4240.198-0ubuntu0.18.04.1
Ubuntu 16.04 LTS·chromium-browser
ESM ended
Fixed: 86.0.4240.198-0ubuntu0.16.04.1
What to do
- Update
chromium-browserto86.0.4240.198-0ubuntu0.18.04.1or later on Ubuntu 18.04 LTS. - On Ubuntu 16.04 LTS, install
86.0.4240.198-0ubuntu0.16.04.1as an interim measure and plan an upgrade to a supported release. - Restart all running browser instances so the patched code is loaded.
- Enable Ubuntu Pro (ESM) on Ubuntu 18.04 LTS systems to keep receiving browser security fixes.
- Apply updates per vendor instructions, as CISA requires for this known exploited flaw.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium-browser with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium-browser"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium-browser"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-416 Use After Free
Questions about CVE-2020-16017
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2020-16017 to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2022-05-03. Whether it has been used in ransomware campaigns is unknown.
- Does updating the package protect browsers that are already open?
- No. Running browser processes keep using the old code. Users must close and restart the browser after the update to be protected.
- What should I do with Ubuntu 16.04 LTS systems?
- A fixed
chromium-browserversion exists, so install it. Ubuntu 16.04 LTS is end of life, though, so upgrade those systems to a supported release to keep receiving security fixes.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.