Google Chrome vulnerabilities: known CVEs & security history
Google · Browser · 1318 tracked CVEs · 4 actively exploited · updated July 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Google Chrome release lines — 1318 in total, with 4 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 1318. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-10585⚡ exploited | critical | 9.8 | 5% | 2025 |
| 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-2026-13782 | critical | 10 | 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-16424 | critical | 9.6 | 0% | 2026 |
| CVE-2026-16419 | critical | 9.6 | 0% | 2026 |
| CVE-2026-15901 | critical | 9.6 | 0% | 2026 |
| CVE-2026-15900 | critical | 9.6 | 0% | 2026 |
| CVE-2026-15899 | critical | 9.6 | 0% | 2026 |
| CVE-2026-15773 | critical | 9.6 | 0% | 2026 |
| CVE-2026-15113 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14425 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14424 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14423 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14420 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14419 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14417 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14416 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14411 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14405 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14398 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14397 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14392 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14390 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14387 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14382 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14152 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14120 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14113 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14109 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14106 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14101 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14097 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14095 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14093 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14056 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14055 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14044 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14043 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14037 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14017 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13934 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13920 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13909 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13901 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13883 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13882 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13880 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13878 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13869 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13861 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13859 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13854 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13853 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13846 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13843 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13798 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13797 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13796 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13792 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13789 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13785 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13781 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13780 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13032 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13028 | critical | 9.6 | 0% | 2026 |
| CVE-2026-12440 | critical | 9.6 | 0% | 2026 |
| CVE-2026-12027 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11697 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11671 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11659 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11654 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11651 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11638 | critical | 9.6 | 0% | 2026 |
1238 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 1318 CVEs for Google Chrome, 4 of which are actively exploited (CISA KEV). 140 are critical-severity and 605 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 — 4 Google Chrome CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild. 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.