| CVE-2017-0561US | critical9.8 | 29.8% (98th) | Exploit | ✗no fix | 2017-04-07 | 2 versions |
| CVE-2017-0781US | high8.8 | 21.5% (98th) | Exploit | ✗no fix | 2017-09-14 | 9 versions |
| CVE-2017-13156US | high7.8 | 20.5% (97th) | Exploit | ✗no fix | 2017-12-06 | 7 versions |
| CVE-2017-0785US | medium6.5 | 12.4% (96th) | Exploit | ✗no fix | 2017-09-14 | 9 versions |
| CVE-2016-10277US | high7.8 | 9.76% (96th) | Exploit | ✗no fix | 2017-05-12 | 2 versions |
| CVE-2017-13208US | critical9.8 | 8.53% (95th) | Exploit | ✗no fix | 2018-01-12 | 8 versions |
| CVE-2017-13262US | medium6.5 | 8.02% (95th) | Exploit | ✗no fix | 2018-04-04 | 8 versions |
| CVE-2017-0569US | high7.0 | 7.69% (95th) | Exploit | ✗no fix | 2017-04-07 | 2 versions |
| CVE-2017-13260US | high7.5 | 7.29% (94th) | Exploit | ✗no fix | 2018-04-04 | 8 versions |
| CVE-2017-13261US | high7.5 | 7.15% (94th) | Exploit | ✗no fix | 2018-04-04 | 8 versions |
| CVE-2017-13258US | high7.5 | 7.12% (94th) | Exploit | ✗no fix | 2018-04-04 | 8 versions |
| CVE-2017-0541US | high7.8 | 4.97% (92nd) | Exploit | ✗no fix | 2017-04-07 | 7 versions |
| CVE-2016-6754US | high8.8 | 4.59% (92nd) | Exploit | ✗no fix | 2016-11-25 | 4 versions |
| CVE-2016-6707US | high7.8 | 4.15% (91st) | Exploit | ✗no fix | 2016-11-25 | 3 versions |
| CVE-2017-0411US | high7.8 | 2.87% (87th) | Exploit | ✗no fix | 2017-02-08 | 2 versions |
| CVE-2017-13253US | high7.8 | 2.81% (86th) | Exploit | ✗no fix | 2018-04-04 | 2 versions |
| CVE-2016-6772US | high7.8 | 2.80% (86th) | Exploit | ✗no fix | 2017-01-12 | 5 versions |
| CVE-2017-0412US | high7.8 | 2.54% (85th) | Exploit | ✗no fix | 2017-02-08 | 2 versions |
| CVE-2017-0478US | high7.8 | 1.84% (79th) | Exploit | ✗no fix | 2017-03-08 | 6 versions |
| CVE-2017-0505US | high7.8 | 1.43% (73rd) | Exploit | ✗no fix | 2017-03-08 | ≤ n/a |
| CVE-2017-0806US | high7.8 | 1.15% (67th) | Exploit | ✗no fix | 2017-10-04 | 6 versions |
| CVE-2017-0554US | high7.8OT elevated | 1.01% (63rd) | Exploit | ✗no fix | 2017-04-07 | 7 versions |
| CVE-2017-13216US | high7.8 | 0.95% (61st) | Exploit | ✗no fix | 2018-01-12 | ≤ Android kernel |
| CVE-2018-9493US | medium5.5 | 0.86% (58th) | Exploit | ✗no fix | 2018-10-02 | ≤ Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9.0 |
| CVE-2018-9445US | medium6.8 | 0.82% (57th) | Exploit | ✗no fix | 2018-11-06 | ≤ Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 |
| CVE-2017-13209US | high7.8OT elevated | 0.75% (55th) | Exploit | ✗no fix | 2018-01-12 | 2 versions |
| CVE-2018-9515US | high7.8 | 0.71% (53rd) | Exploit | ✗no fix | 2018-10-02 | ≤ Android kernel |
| CVE-2017-13236US | high7.8 | 0.55% (46th) | Exploit | ✗no fix | 2018-02-12 | 2 versions |
| CVE-2018-9488US | high7.8OT elevated | 0.43% (37th) | Exploit | ✗no fix | 2018-11-06 | ≤ Android-8.0 Android-8.1 Android-9.0 |
| CVE-2016-8467US | medium5.5 | 0.38% (32nd) | Exploit | ✗no fix | 2017-01-13 | ≤ n/a |
| CVE-2018-9539US | high7.0 | 0.35% (29th) | Exploit | ✗no fix | 2018-11-14 | ≤ Android-8.0 Android-8.1 Android-9 |
| CVE-2016-8462US | medium5.5 | 0.33% (26th) | Exploit | ✗no fix | 2017-01-12 | ≤ n/a |
| CVE-2017-13286US | high7.8 | 0.33% (26th) | Exploit | ✗no fix | 2018-04-04 | 2 versions |
| CVE-2018-9356US | critical9.8 | 3.25% (88th) | — | ✗no fix | 2018-11-06 | ≤ Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 |
| CVE-2018-9355US | critical9.8 | 2.96% (87th) | — | ✗no fix | 2018-11-06 | ≤ Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 |
| CVE-2016-10230US | critical9.8 | 2.95% (87th) | — | ✗no fix | 2018-04-04 | ≤ Android kernel |
| CVE-2018-9450US | high8.8 | 2.74% (86th) | — | ✗no fix | 2018-11-06 | ≤ Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 |
| CVE-2016-8418US | critical9.8 | 2.73% (86th) | — | ✗no fix | 2017-02-08 | ≤ n/a |
| CVE-2018-9503US | high7.5 | 2.63% (85th) | — | ✗no fix | 2018-10-02 | ≤ Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9.0 |
| CVE-2016-6725US | critical9.8 | 2.60% (85th) | — | ✗no fix | 2016-11-25 | 2 versions |
| CVE-2018-9476US | critical9.8 | 2.48% (84th) | — | ✗no fix | 2018-10-02 | ≤ Android-8.0 Android-8.1 |
| CVE-2017-13177US | critical9.8 | 2.42% (84th) | — | ✗no fix | 2018-01-12 | 8 versions |
| CVE-2017-13179US | critical9.8 | 2.35% (84th) | — | ✗no fix | 2018-01-12 | 6 versions |
| CVE-2017-13178US | critical9.8 | 2.35% (84th) | — | ✗no fix | 2018-01-12 | 6 versions |
| CVE-2016-8399US | high7.0 | 2.34% (84th) | — | ✗no fix | 2017-01-12 | 2 versions |
| CVE-2017-0553US | high7.0 | 2.32% (83rd) | — | ✗no fix | 2017-04-07 | 6 versions |
| CVE-2017-0663US | high7.8 | 2.32% (83rd) | — | ✗no fix | 2017-06-14 | ≤ Android-4.4.4 Android-5.0.2 Android-5.1.1 Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 |
| CVE-2017-0540US | high7.8 | 2.32% (83rd) | — | ✗no fix | 2017-04-07 | 6 versions |
| CVE-2016-8438US | critical9.8 | 2.29% (83rd) | — | ✗no fix | 2017-01-12 | ≤ Kernel-3.18 |
| CVE-2016-8440US | critical9.8 | 2.20% (82nd) | — | ✗no fix | 2017-01-12 | ≤ Kernel-3.18 |