| CVE-2020-2509US | critical9.8OT critical | 34.0% (98th) | KEV | ✗no fix | 2021-04-17 | 6 versions |
| CVE-2018-19953US | medium6.1OT critical | 30.5% (98th) | KEV | ✗no fix | 2020-10-28 | 12 versions |
| CVE-2018-19949US | critical9.8OT critical | 30.2% (98th) | KEV | ✗no fix | 2020-10-28 | 12 versions |
| CVE-2018-19943US | medium5.4OT critical | 22.7% (98th) | KEV | ✗no fix | 2020-10-28 | 16 versions |
| CVE-2019-7193US | critical9.8OT critical | 14.4% (97th) | KEV | ✗no fix | 2019-12-05 | 2 versions |
| CVE-2023-47218US | high8.3 | 89.9% (100th) | Exploit | ✗no fix | 2024-02-13 | 8 versions |
| CVE-2017-6360US | critical9.8 | 66.1% (99th) | Exploit | ✗no fix | 2017-03-23 | ≤ 4.2.4 20170313 |
| CVE-2017-6361US | critical9.8 | 56.8% (99th) | Exploit | ✗no fix | 2017-03-23 | ≤ 4.2.4 20170313 |
| CVE-2024-27130US | high8.8 | 37.5% (99th) | Exploit | ✗no fix | 2024-05-21 | — |
| CVE-2017-6359US | critical9.8 | 26.9% (98th) | Exploit | ✗no fix | 2017-03-23 | ≤ 4.2.4 20170313 |
| CVE-2024-53691US | high8.8 | 23.8% (98th) | Exploit | ✗no fix | 2024-12-06 | 5.1.0 → 5.2.0.2802 build 20240620 |
| CVE-2024-21899US | critical9.8 | 24.4% (98th) | — | ✗no fix | 2024-03-08 | 2 versions |
| CVE-2023-23368US | critical9.8 | 18.7% (97th) | — | ✗no fix | 2023-11-03 | 2 versions |
| CVE-2024-21901US | medium4.7 | 18.7% (97th) | — | ✗no fix | 2024-03-08 | 2 versions |
| CVE-2021-28809US | critical9.8OT high | 16.1% (97th) | — | ✗no fix | 2021-07-08 | 3 versions |
| CVE-2023-23369US | critical9.8 | 14.4% (97th) | — | ✗no fix | 2023-11-03 | 5 versions |
| CVE-2023-50358US | — | 13.5% (96th) | — | ✗no fix | 2024-02-13 | 8 versions |
| CVE-2024-21900US | medium6.5 | 9.41% (95th) | — | ✗no fix | 2024-03-08 | 2 versions |
| CVE-2017-7876US | high7.5 | 3.34% (89th) | — | ✗no fix | 2017-06-15 | ≤ 4.2.6 |
| CVE-2022-27596US | critical9.8 | 2.66% (86th) | — | ✗no fix | 2023-01-30 | ≤ 5.0.1.2234 build 20221201 |
| CVE-2020-25847US | high8.8 | 2.58% (85th) | — | ✗no fix | 2020-12-29 | ≤ 4.5.1.1495 |
| CVE-2024-32766US | — | 2.31% (83rd) | — | ✗no fix | 2024-04-26 | 2 versions |
| CVE-2021-34343US | high7.2 | 1.95% (80th) | — | ✗no fix | 2021-09-10 | 4 versions |
| CVE-2020-36195US | critical9.8 | 1.76% (78th) | — | ✗no fix | 2021-04-17 | 2 versions |
| CVE-2021-44051US | high8.8 | 1.66% (77th) | — | ✗no fix | 2022-05-05 | 16 versions |
| CVE-2023-23362US | high8.8 | 1.60% (76th) | — | ✗no fix | 2023-09-22 | 2 versions |
| CVE-2021-44052US | high8.1 | 1.59% (76th) | — | ✗no fix | 2022-05-05 | 15 versions |
| CVE-2021-34344US | critical9.8 | 1.58% (75th) | — | ✗no fix | 2021-09-10 | 2 versions |
| CVE-2023-39296US | high7.5 | 1.56% (75th) | — | ✗no fix | 2024-01-05 | 5.1.0 → 5.1.3.2578 build 20231110 |
| CVE-2023-23367US | high7.2 | 1.50% (74th) | — | ✗no fix | 2023-11-10 | QTS 5.0.0 → 5.0.1.2376 build 20230421 |
| CVE-2023-39297US | high8.8 | 1.41% (72nd) | — | ✗no fix | 2024-02-02 | 2 versions |
| CVE-2021-38687US | critical9.8 | 1.32% (71st) | — | ✗no fix | 2021-12-29 | 3 versions |
| CVE-2024-50393US | critical9.8 | 1.31% (70th) | — | ✗no fix | 2024-12-06 | 2 versions |
| CVE-2023-23355US | high7.2 | 1.23% (69th) | — | ✗no fix | 2023-03-29 | ≤ 5.0.1.2346 build 20230322 |
| CVE-2023-39300US | high7.2 | 1.21% (68th) | — | ✗no fix | 2024-09-06 | 4 versions |
| CVE-2023-47566US | high7.2 | 1.18% (67th) | — | ✗no fix | 2024-02-02 | ≤ 5.1.5.2645 build 20240116 |
| CVE-2023-45025US | critical9.8 | 1.13% (66th) | — | ✗no fix | 2024-02-02 | 2 versions |
| CVE-2023-39294US | high7.2 | 1.12% (66th) | — | ✗no fix | 2024-01-05 | 5.1.0 → 5.1.3.2578 build 20231110 |
| CVE-2023-47567US | high7.2 | 1.11% (66th) | — | ✗no fix | 2024-02-02 | 2 versions |
| CVE-2023-39302US | high7.2 | 1.07% (65th) | — | ✗no fix | 2024-02-02 | 5.1.0 → 5.1.3.2578 build 20231110 |
| CVE-2023-34974US | high8.8 | 0.99% (62nd) | — | ✗no fix | 2024-09-06 | 4.5.0 → 4.5.4.2790 build 20240605 |
| CVE-2023-41283US | high7.2 | 0.97% (62nd) | — | ✗no fix | 2024-02-02 | 5.1.0 → 5.1.4.2596 build 20231128 |
| CVE-2023-41282US | high7.2 | 0.97% (62nd) | — | ✗no fix | 2024-02-02 | 5.1.0 → 5.1.4.2596 build 20231128 |
| CVE-2023-41281US | high7.2 | 0.97% (62nd) | — | ✗no fix | 2024-02-02 | 5.1.0 → 5.1.4.2596 build 20231128 |
| CVE-2025-62849US | critical9.8 | 0.97% (62nd) | — | ✗no fix | 2025-12-16 | ≤ 5.2.7.3297 build 20251024 |
| CVE-2021-38693US | medium5.3 | 0.95% (61st) | — | ✗no fix | 2022-05-05 | 2 versions |
| CVE-2021-28816US | high8.8 | 0.93% (60th) | — | ✗no fix | 2021-09-10 | 4 versions |
| CVE-2023-23363US | critical9.8 | 0.92% (60th) | — | ✗no fix | 2023-09-22 | 4 versions |
| CVE-2023-32975US | high7.2 | 0.87% (59th) | — | ✗no fix | 2023-12-08 | 2 versions |
| CVE-2025-62848US | high7.5 | 0.86% (58th) | — | ✗no fix | 2025-12-16 | ≤ 5.2.7.3297 build 20251024 |