| CVE-2020-3735US | high8.8 | 6.23% (94th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3731US | high8.8 | 6.23% (94th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3740US | critical9.8 | 5.00% (92nd) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2018-15974US | high7.8 | 4.58% (92nd) | — | ✗no fix | 2018-10-17 | ≤ 1.0.5.1 and below versions |
| CVE-2020-9635US | high8.8 | 4.58% (92nd) | — | ✗no fix | 2020-06-12 | ≤ 2019.0.5 and below versions |
| CVE-2020-9634US | high8.8 | 4.58% (92nd) | — | ✗no fix | 2020-06-12 | ≤ 2019.0.5 and below versions |
| CVE-2020-3734US | high8.8 | 4.53% (92nd) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-9636US | high8.8 | 4.04% (91st) | — | ✗no fix | 2020-06-12 | ≤ 2019.0.5 and below versions |
| CVE-2020-3736US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3733US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3728US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3726US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3725US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3724US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3723US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3721US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3720US | high8.8 | 3.97% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3738US | high8.8 | 3.91% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3737US | high8.8 | 3.91% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3732US | high8.8 | 3.91% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3730US | high8.8 | 3.91% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3729US | high8.8 | 3.91% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3727US | high8.8 | 3.91% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3722US | high8.8 | 3.91% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2020-3739US | high8.8 | 3.65% (90th) | — | ✗no fix | 2020-02-13 | ≤ 2019.0.4 and below versions |
| CVE-2024-53959US | — | 0.50% (43rd) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤2022.5 |
| CVE-2024-47421US | — | 0.37% (30th) | — | ✗no fix | 2024-10-09 | ≤ 0 ≤2022.4 |
| CVE-2024-47422US | — | 0.35% (29th) | — | ✗no fix | 2024-10-09 | ≤ 0 ≤2022.4 |
| CVE-2024-30289US | — | 0.34% (27th) | — | ✗no fix | 2024-05-16 | ≤ 0 ≤2022.3 |
| CVE-2024-30288US | — | 0.34% (27th) | — | ✗no fix | 2024-05-16 | ≤ 0 ≤2022.3 |
| CVE-2024-47425US | — | 0.33% (27th) | — | ✗no fix | 2024-10-09 | ≤ 0 ≤2022.4 |
| CVE-2024-47424US | — | 0.33% (27th) | — | ✗no fix | 2024-10-09 | ≤ 0 ≤2022.4 |
| CVE-2024-47423US | — | 0.33% (26th) | — | ✗no fix | 2024-10-09 | ≤ 0 ≤2022.4 |
| CVE-2025-30295US | — | 0.30% (22nd) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2024-30292US | — | 0.28% (21st) | — | ✗no fix | 2024-05-16 | ≤ 0 ≤2022.3 |
| CVE-2024-30291US | — | 0.28% (21st) | — | ✗no fix | 2024-05-16 | ≤ 0 ≤2022.3 |
| CVE-2024-30290US | — | 0.28% (21st) | — | ✗no fix | 2024-05-16 | ≤ 0 ≤2022.3 |
| CVE-2025-30299US | — | 0.27% (20th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2025-30298US | — | 0.27% (20th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2025-47131US | — | 0.25% (16th) | — | ✗no fix | 2025-07-08 | 2 versions |
| CVE-2025-47125US | — | 0.25% (16th) | — | ✗no fix | 2025-07-08 | 2 versions |
| CVE-2025-47123US | — | 0.25% (16th) | — | ✗no fix | 2025-07-08 | 2 versions |
| CVE-2025-47122US | — | 0.25% (16th) | — | ✗no fix | 2025-07-08 | 2 versions |
| CVE-2025-30296US | — | 0.25% (16th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2025-30304US | — | 0.24% (16th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2025-30297US | — | 0.24% (16th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2025-30303US | — | 0.23% (14th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2025-30302US | — | 0.23% (14th) | — | ✗no fix | 2025-04-08 | ≤ 0 ≤2022.6 |
| CVE-2025-47128US | — | 0.23% (14th) | — | ✗no fix | 2025-07-08 | 2 versions |
| CVE-2025-47121US | — | 0.23% (14th) | — | ✗no fix | 2025-07-08 | 2 versions |