| CVE-2024-50302US | medium5.5OT kritisch | 0.81% (57th) | KEV | ✗kein Fix | 2024-11-19 | ≤ vers:unknown/* |
| CVE-2020-1611US | medium6.5 | 1.67% (77th) | Exploit | ✓19.4R1 | 2020-01-15 | unspecified → 19.4R1 |
| CVE-2017-10622US | critical9.8 | 5.39% (93rd) | — | ✗kein Fix | 2017-10-13 | 2 Versionen |
| CVE-2018-0046US | medium6.1 | 1.65% (76th) | — | ✓18.2R1 | 2018-10-10 | unspecified → 18.2R1 |
| CVE-2017-2306US | high8.8OT erhöht | 1.59% (75th) | — | ✗kein Fix | 2017-05-30 | ≤ versions prior to 16.1R1 |
| CVE-2024-39563US | — | 1.34% (71st) | — | ✗kein Fix | 2024-10-11 | ≤ 24.1R1 |
| CVE-2017-2311US | medium5.3 | 1.30% (70th) | — | ✗kein Fix | 2017-05-30 | ≤ versions prior to 16.1R1 |
| CVE-2017-10612US | high8.0 | 1.29% (70th) | — | ✗kein Fix | 2017-10-13 | ≤ versions prior to 17.1R1 |
| CVE-2017-2310US | medium5.3 | 1.24% (69th) | — | ✗kein Fix | 2017-05-30 | ≤ versions prior to 16.1R1 |
| CVE-2018-0013US | medium6.5 | 1.22% (69th) | — | ✓17.2R1 | 2018-01-10 | all → 17.2R1 |
| CVE-2017-2308US | medium6.5 | 1.21% (68th) | — | ✗kein Fix | 2017-05-30 | ≤ versions prior to 16.1R1 |
| CVE-2021-0220US | low3.5 | 1.20% (68th) | — | ✓20.3R1 | 2021-01-15 | unspecified → 20.3R1 |
| CVE-2017-2305US | high8.8OT erhöht | 1.14% (66th) | — | ✗kein Fix | 2017-05-30 | ≤ versions prior to 16.1R1 |
| CVE-2019-0017US | high8.8 | 1.10% (66th) | — | ✓18.3R1 | 2019-01-15 | unspecified → 18.3R1 |
| CVE-2025-60006US | — | 0.99% (62nd) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2019-0016US | medium6.5 | 0.93% (60th) | — | ✓18.3R1 | 2019-01-15 | unspecified → 18.3R1 |
| CVE-2017-10623US | high8.1 | 0.92% (60th) | — | ✗kein Fix | 2017-10-13 | ≤ versions prior to 17.1R1 |
| CVE-2017-2307US | medium6.1 | 0.85% (58th) | — | ✗kein Fix | 2017-05-30 | ≤ versions prior to 16.1R1 |
| CVE-2018-0011US | medium5.4 | 0.83% (57th) | — | ✓17.2R1 | 2018-01-10 | All → 17.2R1 |
| CVE-2017-2309US | medium5.9 | 0.79% (56th) | — | ✗kein Fix | 2017-05-30 | ≤ versions prior to 16.1R1 |
| CVE-2020-1652US | critical9.8 | 0.74% (55th) | — | ✓20.1R1 | 2020-07-17 | 20.1 → 20.1R1 |
| CVE-2026-21906US | — | 0.54% (45th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2025-59978US | — | 0.53% (45th) | — | ✓24.1R4 | 2025-10-09 | 2 Versionen |
| CVE-2025-52961US | — | 0.48% (41st) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2026-21920US | — | 0.48% (41st) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2025-60011US | — | 0.46% (40th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2025-60004US | — | 0.42% (36th) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2025-59975US | — | 0.41% (35th) | — | ✓23.1R1 Patch V3 | 2025-10-09 | 3 Versionen |
| CVE-2026-21917US | — | 0.41% (35th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2025-60003US | — | 0.41% (35th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2025-60001US | — | 0.41% (35th) | — | ✓24.1R4 | 2025-10-09 | 2 Versionen |
| CVE-2025-59990US | — | 0.41% (35th) | — | ✓24.1R4 | 2025-10-09 | 2 Versionen |
| CVE-2025-59988US | — | 0.41% (35th) | — | ✓24.1R4 | 2025-10-09 | 2 Versionen |
| CVE-2025-59984US | — | 0.41% (35th) | — | ✓24.1R4 | 2025-10-09 | 2 Versionen |
| CVE-2026-21918US | — | 0.41% (35th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2026-21913US | — | 0.41% (35th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2026-21905US | — | 0.41% (35th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2026-21903US | — | 0.40% (34th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2026-21921US | — | 0.37% (31st) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2017-10624US | high7.5OT erhöht | 0.36% (30th) | — | ✗kein Fix | 2017-10-13 | ≤ versions prior to 17.1R1 |
| CVE-2025-59964US | — | 0.36% (29th) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2018-0012US | high7.8 | 0.34% (27th) | — | ✓17.2R1 | 2018-01-10 | All → 17.2R1 |
| CVE-2025-52960US | — | 0.33% (26th) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2026-21914US | — | 0.32% (25th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2026-21908US | — | 0.31% (24th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |
| CVE-2025-59968US | —OT erhöht | 0.30% (23rd) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2025-59980US | — | 0.29% (22nd) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2025-59976US | — | 0.29% (21st) | — | ✓24.1R3 | 2025-10-09 | 2 Versionen |
| CVE-2025-59958US | — | 0.28% (20th) | — | ✗kein Fix | 2025-10-09 | ≤ vers:unknown/* |
| CVE-2025-52987US | — | 0.27% (20th) | — | ✗kein Fix | 2026-01-15 | ≤ vers:unknown/* |