Android vulnerabilities: known CVEs & security history
Google · Operating system · 2000 tracked CVEs · 14 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Android release lines — 2000 in total, with 14 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 2000. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2016-1019⚡ exploited | critical | 9.8 | 22% | 2016 |
| CVE-2017-5070⚡ exploited | high | 8.8 | 31% | 2017 |
| CVE-2017-5030⚡ exploited | high | 8.8 | 42% | 2017 |
| CVE-2016-5198⚡ exploited | high | 8.8 | 35% | 2017 |
| CVE-2016-1010⚡ exploited | high | 8.8 | 20% | 2016 |
| CVE-2016-0984⚡ exploited | high | 8.8 | 55% | 2016 |
| CVE-2015-8651⚡ exploited | high | 8.8 | 68% | 2015 |
| CVE-2014-0502⚡ exploited | high | 8.8 | 24% | 2014 |
| CVE-2011-0611⚡ exploited | high | 8.8 | 99% | 2011 |
| CVE-2012-0754⚡ exploited | high | 8.1 | 92% | 2012 |
| CVE-2011-1823⚡ exploited | high | 7.8 | 42% | 2011 |
| CVE-2011-0609⚡ exploited | high | 7.8 | 67% | 2011 |
| CVE-2012-2034⚡ exploited | high | 7.5 | 8% | 2012 |
| CVE-2012-0767⚡ exploited | medium | 6.1 | 7% | 2012 |
| CVE-2015-8459 | critical | 10 | 6% | 2015 |
| CVE-2017-0829 | critical | 9.8 | 0% | 2017 |
| CVE-2017-0828 | critical | 9.8 | 0% | 2017 |
| CVE-2017-0824 | critical | 9.8 | 0% | 2017 |
| CVE-2017-0822 | critical | 9.8 | 0% | 2017 |
| CVE-2017-0807 | critical | 9.8 | 2% | 2017 |
| CVE-2017-7364 | critical | 9.8 | 1% | 2017 |
| CVE-2016-5872 | critical | 9.8 | 1% | 2017 |
| CVE-2016-5871 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10392 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10391 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10390 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10388 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10387 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10386 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10385 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10384 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10382 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10381 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10380 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10347 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10346 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10344 | critical | 9.8 | 1% | 2017 |
| CVE-2016-10343 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9073 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9072 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9071 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9070 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9069 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9068 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9067 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9066 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9065 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9064 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9063 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9062 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9061 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9060 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9055 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9054 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9053 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9052 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9051 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9050 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9049 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9048 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9047 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9046 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9045 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9044 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9043 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9042 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9041 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9040 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9039 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9038 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9037 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9036 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9035 | critical | 9.8 | 1% | 2017 |
| CVE-2015-9034 | critical | 9.8 | 1% | 2017 |
| CVE-2015-8596 | critical | 9.8 | 1% | 2017 |
| CVE-2015-8595 | critical | 9.8 | 1% | 2017 |
| CVE-2015-8594 | critical | 9.8 | 1% | 2017 |
| CVE-2015-8593 | critical | 9.8 | 1% | 2017 |
| CVE-2015-8592 | critical | 9.8 | 1% | 2017 |
| CVE-2015-0575 | critical | 9.8 | 1% | 2017 |
1920 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 2000 CVEs for Android, 14 of which are actively exploited (CISA KEV). 146 are critical-severity and 1351 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 — 14 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.