| CVE-2025-15467US | — | 74.8% (100th) | Exploit | ✗kein Fix | 2026-01-27 | 2 Versionen |
| CVE-2025-6965US | high7.7 | 73.5% (99th) | Exploit | ✗kein Fix | 2025-07-15 | ≤ vers:unknown/* |
| CVE-2024-1305US | — | 15.4% (97th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-24974US | high7.5 | 9.76% (95th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-27903US | critical9.8 | 8.92% (95th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-27459US | high7.8 | 8.26% (95th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-5594US | — | 0.82% (57th) | — | ✗kein Fix | 2025-01-06 | ≤ vers:unknown/<v31.01.07 |
| CVE-2025-27394US | — | 0.73% (54th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2025-27393US | — | 0.73% (54th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2025-27392US | — | 0.73% (54th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-28882US | — | 0.66% (52nd) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v31.01.07 |
| CVE-2025-27395US | medium6.5 | 0.66% (51st) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-42512US | — | 0.60% (48th) | — | ✗kein Fix | 2025-02-10 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-42513US | — | 0.58% (47th) | — | ✗kein Fix | 2025-02-10 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-56336US | — | 0.55% (46th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2025-71316US | — | 0.54% (45th) | — | ✗kein Fix | 2026-06-04 | ≤ vers:unknown/* |
| CVE-2026-10207US | — | 0.51% (43rd) | — | ✗kein Fix | 2026-07-28 | ≤ vers:unknown/* |
| CVE-2025-27494US | high7.2 | 0.50% (43rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2026-44415DE | critical9.1 | 0.48% (41st) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-44414DE | medium6.8 | 0.47% (40th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2025-70873US | — | 0.46% (39th) | — | ✗kein Fix | 2026-03-12 | ≤ vers:unknown/* |
| CVE-2024-41046US | high7.8 | 0.45% (39th) | — | ✗kein Fix | 2024-07-29 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-52285US | —OT erhöht | 0.45% (39th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2025-27396US | — | 0.44% (38th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2024-4877US | — | 0.43% (37th) | — | ✗kein Fix | 2025-04-03 | ≤ vers:unknown/<v31.01.07 |
| CVE-2026-46746US | — | 0.43% (37th) | — | ✗kein Fix | 2026-06-09 | ≤ vers:unknown/* |
| CVE-2026-33388US | —OT erhöht | 0.41% (35th) | — | ✗kein Fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2025-27397US | — | 0.41% (35th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2026-11822US | — | 0.36% (30th) | — | ✗kein Fix | 2026-06-09 | ≤ vers:unknown/* |
| CVE-2026-33391US | —OT erhöht | 0.36% (29th) | — | ✗kein Fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2024-7322US | — | 0.34% (27th) | — | ✗kein Fix | 2025-01-15 | ≤ vers:unknown/* |
| CVE-2026-59241DE | high8.8 | 0.34% (27th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2025-27398US | — | 0.34% (27th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2026-63350DE | critical9.6 | 0.34% (27th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-85114DE | high7.5 | 0.33% (26th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-78557DE | high8.3 | 0.32% (24th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-63354DE | critical9.6 | 0.31% (24th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-63353DE | critical9.6 | 0.31% (24th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-89198DE | high8.8 | 0.30% (23rd) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-89197DE | high8.8 | 0.30% (22nd) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-89196DE | high8.8 | 0.30% (22nd) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2024-41049US | high7.0 | 0.28% (20th) | — | ✗kein Fix | 2024-07-29 | ≤ vers:unknown/<v31.01.07 |
| CVE-2025-23384US | — | 0.28% (20th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v31.01.07 |
| CVE-2026-89208DE | medium5.3 | 0.26% (18th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2024-42154US | medium4.4 | 0.26% (18th) | — | ✗kein Fix | 2024-07-30 | ≤ vers:unknown/<v31.01.07 |
| CVE-2026-33387US | — | 0.26% (17th) | — | ✗kein Fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2024-41055US | medium5.5 | 0.26% (17th) | — | ✗kein Fix | 2024-07-29 | ≤ vers:unknown/<v31.01.07 |
| CVE-2026-89199DE | high8.8 | 0.25% (16th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2026-46747US | medium5.3 | 0.24% (15th) | — | ✗kein Fix | 2026-06-09 | ≤ vers:unknown/* |
| CVE-2026-89201DE | high7.5 | 0.24% (14th) | — | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |