Product · KEV exposure
Google Chrome known exploited vulnerabilities
We track 7 CVEs in Google Chrome. 2 of them are on CISA's Known Exploited Vulnerabilities catalog, meaning CISA has evidence of exploitation in the wild (listed 2021–2021). The most recent is CVE-2026-106382.
- CVEs tracked
- 7
- On CISA KEV
- 2
- Ransomware use
- 0
- Rated critical
- 4
Every Google Chrome CVE we track
| CVE / Vulnerability | Severity | CVSS | EPSS | Added to KEV | Patch by |
|---|---|---|---|---|---|
| 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% | — | — |
| CVE-2020-16017 Google Chrome Use-After-Free Vulnerability | [ CRITICAL ] | 9.6 | 2.7% |
Sorted by date added to KEV. Severity and CVSS as stated by NVD or the vendor; EPSS from FIRST.org. "Patch by" is CISA's BOD 22-01 deadline for US federal agencies, a useful priority signal for everyone else. Machine-readable: /api/v1/vendors/google.json.
Our Google Chrome coverage
Other Google products
Every row links to its CVE record with the CISA required action, catalog coverage and primary sources. We describe impact and remediation only; no exploit code. See the full KEV tracker or compare KEV catalogs.