VDB
CVE-2020-16016
CVE-2020-16016
PUBLISHED
Reported by chrome · Published January 8, 2021
Inappropriate implementation in base in Google Chrome prior to 86.0.4240.193 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| chromium | Arch Linux | 86.0.4240.193-1 |
| chrome | 86.0.4240.193 | |
| chromium-browser | Ubuntu:16.04:LTS | 86.0.4240.198-0ubuntu0.16.04.1 |
| chromium-browser | Ubuntu:18.04:LTS | 86.0.4240.198-0ubuntu0.18.04.1 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Chrome | unspecified | |
| Chrome | * | |
| arch | chromium | 0 |
Timeline
- Nov 15, 2020 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Aug 4, 2024 CVE Updated
- Jun 2, 2026 Security Advisory (5 in total, the first dated here)
- Sep 4, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2020-16016
vulnetix vdb fixes CVE-2020-16016Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-16016/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart