Google Chrome vulnerabilities: known CVEs & security history
Google · Browser · 2345 tracked CVEs · 7 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Google Chrome release lines — 2345 in total, with 7 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Google Chrome's current status and the safe version to run.
Known Google Chrome CVEs
Actively-exploited and most-severe first. Showing the top 80 of 2345. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-10585⚡ exploited | critical | 9.8 | 5% | 2025 |
| CVE-2026-87491⚡ exploited | high | 8.8 | 1% | 2026 |
| CVE-2026-85046⚡ exploited | high | 8.8 | 1% | 2026 |
| CVE-2026-11645⚡ exploited | high | 8.8 | 2% | 2026 |
| CVE-2026-5281⚡ exploited | high | 8.8 | 5% | 2026 |
| CVE-2025-13223⚡ exploited | high | 8.8 | 5% | 2025 |
| CVE-2022-2294⚡ exploited | high | 8.8 | 70% | 2022 |
| CVE-2026-13782 | critical | 10 | 0% | 2026 |
| CVE-2026-87544 | critical | 9.8 | 0% | 2026 |
| CVE-2026-87534 | critical | 9.8 | 0% | 2026 |
| CVE-2026-84325 | critical | 9.8 | 0% | 2026 |
| CVE-2026-79152 | critical | 9.8 | 0% | 2026 |
| CVE-2026-79090 | critical | 9.8 | 0% | 2026 |
| CVE-2026-14121 | critical | 9.8 | 0% | 2026 |
| CVE-2026-14104 | critical | 9.8 | 0% | 2026 |
| CVE-2026-13776 | critical | 9.8 | 0% | 2026 |
| CVE-2026-13775 | critical | 9.8 | 0% | 2026 |
| CVE-2026-5902 | critical | 9.8 | 0% | 2026 |
| CVE-2026-87654 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87650 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87646 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87643 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87638 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87637 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87634 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87621 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87609 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87607 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87581 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87558 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87547 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87529 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87528 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87527 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87526 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87520 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87512 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87504 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87500 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87494 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87492 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87488 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87474 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87470 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87464 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87455 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87448 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87438 | critical | 9.6 | 0% | 2026 |
| CVE-2026-85050 | critical | 9.6 | 0% | 2026 |
| CVE-2026-85047 | critical | 9.6 | 0% | 2026 |
| CVE-2026-85042 | critical | 9.6 | 0% | 2026 |
| CVE-2026-84354 | critical | 9.6 | 0% | 2026 |
| CVE-2026-84353 | critical | 9.6 | 0% | 2026 |
| CVE-2026-84352 | critical | 9.6 | 0% | 2026 |
| CVE-2026-84333 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79290 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79282 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79275 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79257 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79235 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79232 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79200 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79189 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79188 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79150 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79149 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79140 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79138 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79131 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79130 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79129 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79128 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79111 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79091 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79078 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79064 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79056 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79052 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79047 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79043 | critical | 9.6 | 0% | 2026 |
2265 older / lower-severity CVEs not shown — see Google Chrome's full record.
Is my Google Chrome version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Google Chrome version → · Monitor Google Chrome for new CVEs →
Google Chrome vulnerabilities — frequently asked
How many known vulnerabilities does Google Chrome have?
IsItPatched tracks 2345 CVEs for Google Chrome, 7 of which are actively exploited (CISA KEV). 292 are critical-severity and 875 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Google Chrome have any actively-exploited vulnerabilities?
Yes — 7 Google Chrome CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (1 linked to ransomware). Patch these as a priority.
What is the most severe Google Chrome vulnerability?
Among tracked issues, CVE-2025-10585 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a CWE-843 weakness.
Is Google Chrome safe to use?
It depends on the version. The latest supported Google Chrome release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Google Chrome security status · Google Chrome end-of-life · actively-exploited CVEs. Always verify against Google's advisories — see our disclaimer.