| CVE-2025-54253US | —OT critical | 88.8% (100th) | KEV | ✗no fix | 2025-08-05 | 2 versions |
| CVE-2025-47029US | — | 0.36% (30th) | Exploit | ✗no fix | 2025-06-10 | ≤ 0 ≤6.5.22 |
| CVE-2025-54254US | high8.6 | 70.1% (99th) | — | ✗no fix | 2025-08-05 | 2 versions |
| CVE-2019-8086US | high7.5 | 22.5% (98th) | — | ✗no fix | 2019-10-25 | 4 versions |
| CVE-2019-16469US | high7.5 | 17.2% (97th) | — | ✗no fix | 2020-01-15 | ≤ 6.5, 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2019-7964US | critical9.8 | 10.2% (96th) | — | ✗no fix | 2019-08-16 | ≤ 6.5, and 6.4 versions |
| CVE-2025-54248US | — | 6.48% (94th) | — | ✗no fix | 2025-09-09 | 2 versions |
| CVE-2019-8088US | critical9.8 | 5.76% (93rd) | — | ✗no fix | 2019-10-25 | ≤ 6.5, 6.4, 6.3, 6.2 |
| CVE-2025-54252US | — | 5.62% (93rd) | — | ✗no fix | 2025-09-09 | 2 versions |
| CVE-2019-8087US | high7.5 | 3.65% (90th) | — | ✗no fix | 2019-10-25 | ≤ 6.5, 6.4, 6.3, 6.2 |
| CVE-2019-8081US | high7.5 | 3.30% (88th) | — | ✗no fix | 2019-10-25 | ≤ 6.5, 6.4, 6.3, 6.2 |
| CVE-2020-9645US | high7.5 | 3.29% (88th) | — | ✗no fix | 2020-06-12 | ≤ 6.5 and earlier versions |
| CVE-2020-9643US | high7.5 | 3.29% (88th) | — | ✗no fix | 2020-06-12 | ≤ 6.5 and earlier versions |
| CVE-2020-3741US | high7.5 | 3.21% (88th) | — | ✗no fix | 2020-02-13 | ≤ 6.5, and 6.4 versions |
| CVE-2019-8082US | high7.5 | 3.19% (88th) | — | ✗no fix | 2019-10-25 | ≤ 6.4, 6.3, 6.2 |
| CVE-2020-3769US | high7.5 | 2.85% (87th) | — | ✗no fix | 2020-03-25 | ≤ 6.5 and earlier versions |
| CVE-2019-16468US | high7.5 | 2.63% (85th) | — | ✗no fix | 2020-01-15 | ≤ 6.5, 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2020-9651US | medium6.1 | 2.44% (84th) | — | ✗no fix | 2020-06-12 | ≤ 6.5 and earlier versions |
| CVE-2020-9648US | medium6.1 | 2.44% (84th) | — | ✗no fix | 2020-06-12 | ≤ 6.5 and earlier versions |
| CVE-2020-9647US | medium6.1 | 2.44% (84th) | — | ✗no fix | 2020-06-12 | ≤ 6.5 and earlier versions |
| CVE-2018-15972US | medium6.1 | 2.41% (84th) | — | ✗no fix | 2018-10-17 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2018-15973US | medium6.1 | 2.38% (84th) | — | ✗no fix | 2018-10-17 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2019-8234US | medium6.5 | 2.15% (82nd) | — | ✗no fix | 2019-10-25 | ≤ 6.4, 6.3, 6.2 |
| CVE-2018-19727US | medium6.1 | 1.94% (80th) | — | ✗no fix | 2019-01-28 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2018-19726US | medium6.1 | 1.94% (80th) | — | ✗no fix | 2019-01-28 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2018-15971US | medium6.1 | 1.94% (80th) | — | ✗no fix | 2018-10-17 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2018-15970US | medium6.1 | 1.94% (80th) | — | ✗no fix | 2018-10-17 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2018-15969US | medium6.1 | 1.94% (80th) | — | ✗no fix | 2018-10-17 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2025-54249US | — | 1.92% (80th) | — | ✗no fix | 2025-09-09 | 2 versions |
| CVE-2019-8080US | medium6.1 | 1.77% (78th) | — | ✗no fix | 2019-10-24 | ≤ 6.4, 6.3 |
| CVE-2020-9644US | medium5.4 | 1.76% (78th) | — | ✗no fix | 2020-06-12 | ≤ 6.5 and earlier versions |
| CVE-2025-54251US | — | 1.71% (77th) | — | ✗no fix | 2025-09-09 | 2 versions |
| CVE-2019-8078US | medium6.1 | 1.61% (76th) | — | ✗no fix | 2019-10-24 | ≤ 6.4, 6.3, 6.2 |
| CVE-2019-16467US | medium6.1 | 1.50% (74th) | — | ✗no fix | 2020-01-15 | ≤ 6.5, 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2019-16466US | medium6.1 | 1.50% (74th) | — | ✗no fix | 2020-01-15 | ≤ 6.5, 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2019-8085US | medium6.1 | 1.50% (74th) | — | ✗no fix | 2019-10-25 | ≤ 6.5, 6.4, 6.3, 6.2 |
| CVE-2019-8084US | medium6.1 | 1.50% (74th) | — | ✗no fix | 2019-10-25 | ≤ 6.5, 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2019-8083US | medium6.1 | 1.50% (74th) | — | ✗no fix | 2019-10-25 | ≤ 6.5, 6.4, 6.3 |
| CVE-2019-8079US | medium6.1 | 1.50% (74th) | — | ✗no fix | 2019-10-24 | ≤ 6.4, 6.3, 6.2, 6.1, and 6.0 versions |
| CVE-2024-43729US | medium6.5 | 1.07% (65th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-26029US | critical9.8 | 1.01% (63rd) | — | ✗no fix | 2024-06-13 | ≤ 0 ≤6.5.20 |
| CVE-2024-52831US | low3.5 | 0.94% (61st) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-43755US | low3.5 | 0.94% (61st) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-52844US | — | 0.90% (59th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-52840US | — | 0.90% (59th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-52839US | — | 0.90% (59th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-52838US | — | 0.90% (59th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-52837US | — | 0.90% (59th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-52823US | — | 0.90% (59th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |
| CVE-2024-52822US | — | 0.90% (59th) | — | ✗no fix | 2024-12-10 | ≤ 0 ≤6.5.21 |