| CVE-2024-32459US | critical9.8 | 3.72% (90th) | Exploit | ✗no fix | 2024-04-22 | 2 versions |
| CVE-2020-11019US | medium6.5 | 2.28% (83rd) | Exploit | ✗no fix | 2020-05-29 | ≤ ≤ 2.0.0 |
| CVE-2020-11097US | medium5.4 | 1.36% (72nd) | Exploit | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2026-45700US | critical9.8 | 6.10% (93rd) | — | ✗no fix | 2026-05-29 | ≤ < 3.26.0 |
| CVE-2026-44420US | — | 4.56% (92nd) | — | ✗no fix | 2026-05-29 | ≤ < 3.26.0 |
| CVE-2022-24882US | high7.5 | 2.85% (87th) | — | ✗no fix | 2022-04-26 | ≤ < 2.7.0 |
| CVE-2022-24883US | critical9.8 | 2.34% (84th) | — | ✗no fix | 2022-04-26 | ≤ < 2.7.0 |
| CVE-2024-32039US | critical9.8 | 2.27% (83rd) | — | ✗no fix | 2024-04-22 | 2 versions |
| CVE-2020-11099US | medium6.5 | 2.13% (82nd) | — | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2020-11043US | low2.7 | 1.96% (80th) | — | ✗no fix | 2020-05-29 | ≤ ≤ 2.0.0 |
| CVE-2024-32458US | critical9.8 | 1.94% (80th) | — | ✗no fix | 2024-04-22 | 2 versions |
| CVE-2024-32041US | critical9.8 | 1.93% (80th) | — | ✗no fix | 2024-04-22 | 3 versions |
| CVE-2024-32460US | critical9.8 | 1.91% (80th) | — | ✗no fix | 2024-04-22 | 2 versions |
| CVE-2024-32040US | critical9.8 | 1.91% (80th) | — | ✗no fix | 2024-04-22 | 2 versions |
| CVE-2020-11018US | medium6.5 | 1.90% (80th) | — | ✗no fix | 2020-05-29 | ≤ ≤ 2.0.0 |
| CVE-2020-11048US | low2.2 | 1.85% (79th) | — | ✓2.0.0 | 2020-05-07 | > 1.0, → 2.0.0 |
| CVE-2020-4032US | medium4.3 | 1.84% (79th) | — | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2020-11096US | medium6.5 | 1.84% (79th) | — | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2023-39356US | critical9.1 | 1.81% (78th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2020-11042US | medium5.9 | 1.77% (78th) | — | ✓2.0.0 | 2020-05-07 | > 1.1, → 2.0.0 |
| CVE-2017-2834US | high7.0 | 1.76% (78th) | — | ✗no fix | 2018-04-24 | ≤ 2.0.0-beta1+android11 - Windows, OSX, Linux |
| CVE-2020-4033US | medium6.5 | 1.76% (78th) | — | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2020-11085US | low3.5 | 1.75% (78th) | — | ✗no fix | 2020-05-29 | ≤ < 2.1.0 |
| CVE-2020-11047US | medium5.9 | 1.71% (77th) | — | ✓2.0.0 | 2020-05-07 | > 1.1, → 2.0.0 |
| CVE-2020-11045US | low3.3 | 1.70% (77th) | — | ✓2.0.0 | 2020-05-07 | > 1.0, → 2.0.0 |
| CVE-2023-40181US | critical9.1 | 1.69% (77th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2020-11044US | low2.2 | 1.69% (77th) | — | ✓2.0.0 | 2020-05-07 | > 1.2, → 2.0.0 |
| CVE-2021-41160US | high8.8 | 1.66% (77th) | — | ✗no fix | 2021-10-21 | ≤ < 2.4.1 |
| CVE-2020-4030US | medium6.5 | 1.66% (77th) | — | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2020-11017US | medium6.5 | 1.65% (76th) | — | ✗no fix | 2020-05-29 | ≤ ≤ 2.0.0 |
| CVE-2023-39350US | high7.5 | 1.64% (76th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2020-11098US | medium6.5 | 1.61% (76th) | — | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2020-4031US | high7.5 | 1.61% (76th) | — | ✗no fix | 2020-06-22 | ≤ < 2.1.2 |
| CVE-2020-11058US | low2.2 | 1.61% (76th) | — | ✓2.0.0 | 2020-05-12 | > 1.1, → 2.0.0 |
| CVE-2020-11040US | low2.7 | 1.61% (76th) | — | ✗no fix | 2020-05-29 | ≤ ≤ 2.0.0 |
| CVE-2023-39354US | high7.5 | 1.58% (75th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2023-39351US | high7.5 | 1.56% (75th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2017-2839US | medium5.9 | 1.55% (75th) | — | ✗no fix | 2018-04-24 | ≤ 2.0.0-beta1+android11 - Windows, OSX, Linux |
| CVE-2023-39352US | critical9.8 | 1.54% (75th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2017-2838US | medium5.9 | 1.52% (74th) | — | ✗no fix | 2018-04-24 | ≤ 2.0.0-beta1+android11 - Windows, OSX, Linux |
| CVE-2017-2837US | medium5.9 | 1.52% (74th) | — | ✗no fix | 2018-04-24 | ≤ 2.0.0-beta1+android11 - Windows, OSX, Linux |
| CVE-2020-11049US | low2.2 | 1.52% (74th) | — | ✓2.0.0 | 2020-05-07 | > 1.1, → 2.0.0 |
| CVE-2023-40567US | critical9.8 | 1.50% (74th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2021-41159US | high8.8 | 1.49% (74th) | — | ✗no fix | 2021-10-21 | ≤ < 2.4.1 |
| CVE-2023-40188US | critical9.1 | 1.48% (74th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2023-39353US | critical9.1 | 1.48% (74th) | — | ✓3.0.0-beta3 | 2023-08-31 | 2 versions |
| CVE-2020-15103US | low3.5 | 1.46% (73rd) | — | ✗no fix | 2020-07-27 | ≤ ≤ 2.1.2 |
| CVE-2017-2835US | high8.1 | 1.43% (73rd) | — | ✗no fix | 2018-04-24 | ≤ 2.0.0-beta1+android11 - Windows, OSX, Linux |
| CVE-2020-11088US | medium5.4 | 1.43% (73rd) | — | ✗no fix | 2020-05-29 | ≤ ≤ 2.0.0 |
| CVE-2020-11087US | medium5.4 | 1.43% (73rd) | — | ✗no fix | 2020-05-29 | ≤ ≤ 2.0.0 |