Google Chrome Use-After-Free Vulnerability
Google Chrome contains a use-after-free vulnerability that allows a remote attacker, who has compromised the renderer process, to potentially perform a sandbox escape via a crafted HTML page.
- Vendor
- Product
- Chrome
- CVSS
- 9.6
- EPSS (exploit probability)
- 2.7%
- Status
- kev
- CISA patch-by (BOD 22-01)
- Added to KEV
Is CVE-2020-16017 being exploited?
Yes. CISA added CVE-2020-16017 to its Known Exploited Vulnerabilities catalog on . CISA only lists a CVE when it has reliable evidence of exploitation in the wild.
FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 2.7% (scored October 14, 2026).
- CISA KEV[ LISTED ]
- ENISA EUVD (exploited)[ — ]
- CIRCL KEV[ — ]
Catalog snapshot 2026-10-19. Full cross-catalog view: /kev-comparison
What to do
CISA required actionApply updates per vendor instructions.
US federal civilian agencies must remediate by (181 days after listing) under BOD 22-01. Everyone else: that deadline is a sensible upper bound, not a target. Vendor guidance and the NVD record are linked under Source above.
Other Google Chrome CVEs we track
| CVE / Vulnerability | Severity | CVSS | EPSS | Added to KEV |
|---|---|---|---|---|
| CVE-2026-106382 Use-after-free in Chromecast allows sandbox code executionwrite-up | [ CRITICAL ] | 9.6 | 0.4% | — |
| CVE-2026-106358 Use-after-free in Chrome Navigation allows sandbox code executionwrite-up | [ CRITICAL ] | 9.6 | 0.5% | — |
| CVE-2026-106347 Use-after-free in Chrome Track component allows sandbox code executionwrite-up | [ HIGH ] | 8.8 | 0.4% | — |
| CVE-2026-106197 Use-after-free in Chrome Browser component enables sandbox RCEwrite-up | [ CRITICAL ] | 9.6 | 0.5% | — |
| CVE-2026-85046 Type confusion in Chrome V8 allows sandbox code executionwrite-up | [ HIGH ] | 8.8 | 48.9% | |
| CVE-2026-15765 Chrome Ozone use-after-freewrite-up | [ HIGH ] | 7.5 | 0.5% | — |