Google Chrome vulnerabilities: known CVEs & security history
Google · Browser · 3575 tracked CVEs · 10 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Google Chrome release lines — 3575 in total, with 10 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 3575. 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-14174⚡ exploited | high | 8.8 | 22% | 2025 |
| CVE-2025-13223⚡ exploited | high | 8.8 | 5% | 2025 |
| CVE-2025-6558⚡ exploited | high | 8.8 | 10% | 2025 |
| CVE-2023-3079⚡ exploited | high | 8.8 | 32% | 2023 |
| CVE-2022-2294⚡ exploited | high | 8.8 | 70% | 2022 |
| CVE-2026-13782 | critical | 10 | 0% | 2026 |
| CVE-2026-87595 | critical | 9.8 | 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 | 1% | 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-113342 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113336 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113328 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113300 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113283 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113270 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113263 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113261 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113252 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113235 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113222 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113211 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113189 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113186 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113171 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113169 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113138 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113126 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113116 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113089 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113084 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113078 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113072 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113056 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113023 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113020 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113014 | critical | 9.6 | 0% | 2026 |
| CVE-2026-113007 | critical | 9.6 | 0% | 2026 |
| CVE-2026-112992 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110916 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110165 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110161 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110159 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110152 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110149 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110142 | critical | 9.6 | 0% | 2026 |
| CVE-2026-110136 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106419 | critical | 9.6 | — | 2026 |
| CVE-2026-106417 | critical | 9.6 | — | 2026 |
| CVE-2026-106414 | critical | 9.6 | — | 2026 |
| CVE-2026-106401 | critical | 9.6 | — | 2026 |
| CVE-2026-106382 | critical | 9.6 | — | 2026 |
| CVE-2026-106375 | critical | 9.6 | — | 2026 |
| CVE-2026-106372 | critical | 9.6 | — | 2026 |
| CVE-2026-106358 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106329 | critical | 9.6 | — | 2026 |
| CVE-2026-106323 | critical | 9.6 | — | 2026 |
| CVE-2026-106298 | critical | 9.6 | — | 2026 |
| CVE-2026-106281 | critical | 9.6 | — | 2026 |
| CVE-2026-106241 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106239 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106237 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106234 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106227 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106211 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106197 | critical | 9.6 | 0% | 2026 |
| CVE-2026-102322 | critical | 9.6 | 0% | 2026 |
| CVE-2026-103630 | critical | 9.6 | 0% | 2026 |
3495 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 3575 CVEs for Google Chrome, 10 of which are actively exploited (CISA KEV). 402 are critical-severity and 1525 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 — 10 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.