Android vulnerabilities: known CVEs & security history
Google · Operating system · 828 tracked CVEs · 5 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Android release lines — 828 in total, with 5 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Android's current status and the safe version to run.
Known Android CVEs
Actively-exploited and most-severe first. Showing the top 80 of 828. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2016-1019⚡ exploited | critical | 9.8 | 22% | 2016 |
| CVE-2026-58704⚡ exploited | high | 8.8 | 1% | 2026 |
| CVE-2025-48595⚡ exploited | high | 8.4 | 2% | 2026 |
| CVE-2025-48572⚡ exploited | high | 7.8 | 0% | 2025 |
| CVE-2025-48633⚡ exploited | medium | 5.5 | 0% | 2025 |
| CVE-2026-56960 | critical | 9.8 | 0% | 2026 |
| CVE-2026-55366 | critical | 9.8 | 0% | 2026 |
| CVE-2026-87534 | critical | 9.8 | 0% | 2026 |
| CVE-2026-58822 | critical | 9.8 | 0% | 2026 |
| CVE-2026-49921 | critical | 9.8 | 0% | 2026 |
| CVE-2026-28606 | critical | 9.8 | 0% | 2026 |
| CVE-2026-79152 | critical | 9.8 | 0% | 2026 |
| CVE-2026-0163 | critical | 9.8 | 1% | 2026 |
| CVE-2026-16280 | critical | 9.8 | 0% | 2026 |
| CVE-2026-0126 | critical | 9.8 | 0% | 2026 |
| CVE-2026-30789 | critical | 9.8 | 0% | 2026 |
| CVE-2026-30783 | critical | 9.8 | 0% | 2026 |
| CVE-2025-36937 | critical | 9.8 | 0% | 2025 |
| CVE-2025-48626 | critical | 9.8 | 0% | 2025 |
| CVE-2025-8042 | critical | 9.8 | 0% | 2025 |
| CVE-2026-106419 | critical | 9.6 | — | 2026 |
| CVE-2026-106241 | critical | 9.6 | 0% | 2026 |
| CVE-2026-106239 | critical | 9.6 | 0% | 2026 |
| CVE-2026-102331 | critical | 9.6 | — | 2026 |
| CVE-2026-95357 | critical | 9.6 | — | 2026 |
| CVE-2026-95350 | critical | 9.6 | — | 2026 |
| CVE-2026-95349 | critical | 9.6 | — | 2026 |
| CVE-2026-95329 | critical | 9.6 | — | 2026 |
| CVE-2026-95284 | critical | 9.6 | 0% | 2026 |
| CVE-2026-95283 | critical | 9.6 | — | 2026 |
| CVE-2026-95281 | critical | 9.6 | — | 2026 |
| CVE-2026-93374 | critical | 9.6 | 0% | 2026 |
| CVE-2026-93372 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87643 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87520 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87488 | critical | 9.6 | 0% | 2026 |
| CVE-2026-87438 | critical | 9.6 | 0% | 2026 |
| CVE-2026-85050 | 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-79282 | critical | 9.6 | 0% | 2026 |
| CVE-2026-79129 | critical | 9.6 | 0% | 2026 |
| CVE-2026-78937 | critical | 9.6 | 0% | 2026 |
| CVE-2026-76036 | critical | 9.6 | 1% | 2026 |
| CVE-2026-19170 | critical | 9.6 | 0% | 2026 |
| CVE-2026-19157 | critical | 9.6 | 0% | 2026 |
| CVE-2026-17940 | critical | 9.6 | 0% | 2026 |
| CVE-2026-17727 | critical | 9.6 | 0% | 2026 |
| CVE-2026-17726 | critical | 9.6 | 0% | 2026 |
| CVE-2026-17713 | critical | 9.6 | 0% | 2026 |
| CVE-2026-17681 | critical | 9.6 | 0% | 2026 |
| CVE-2026-17676 | critical | 9.6 | 0% | 2026 |
| CVE-2026-17651 | critical | 9.6 | 0% | 2026 |
| CVE-2026-16424 | critical | 9.6 | 0% | 2026 |
| CVE-2026-16419 | critical | 9.6 | 0% | 2026 |
| CVE-2026-15900 | critical | 9.6 | 0% | 2026 |
| CVE-2026-15113 | critical | 9.6 | 0% | 2026 |
| CVE-2026-14106 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13032 | critical | 9.6 | 0% | 2026 |
| CVE-2026-13028 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11167 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11163 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11131 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11119 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11082 | critical | 9.6 | 0% | 2026 |
| CVE-2026-11029 | critical | 9.6 | 0% | 2026 |
| CVE-2026-10892 | critical | 9.6 | 0% | 2026 |
| CVE-2026-9876 | critical | 9.6 | 0% | 2026 |
| CVE-2026-9875 | critical | 9.6 | 0% | 2026 |
| CVE-2026-9872 | critical | 9.6 | 0% | 2026 |
| CVE-2026-34691 | critical | 9.3 | 0% | 2026 |
| CVE-2026-13872 | critical | 9.1 | 0% | 2026 |
| CVE-2026-13852 | critical | 9.1 | 0% | 2026 |
| CVE-2026-13851 | critical | 9.1 | 0% | 2026 |
| CVE-2025-11717 | critical | 9.1 | 0% | 2025 |
| CVE-2026-106371 | high | 8.8 | — | 2026 |
| CVE-2026-106308 | high | 8.8 | — | 2026 |
| CVE-2026-106256 | high | 8.8 | — | 2026 |
| CVE-2026-106249 | high | 8.8 | — | 2026 |
748 older / lower-severity CVEs not shown — see Android's full record.
Is my Android 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 Android version → · Monitor Android for new CVEs →
Android vulnerabilities — frequently asked
How many known vulnerabilities does Android have?
IsItPatched tracks 828 CVEs for Android, 5 of which are actively exploited (CISA KEV). 72 are critical-severity and 374 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Android have any actively-exploited vulnerabilities?
Yes — 5 Android 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 Android vulnerability?
Among tracked issues, CVE-2016-1019 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest.
Is Android safe to use?
It depends on the version. The latest supported Android 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: Android security status · Android end-of-life · actively-exploited CVEs. Always verify against Google's advisories — see our disclaimer.