| CVE-2025-1974US | — | 99.4% (100th) | Exploit | ✗kein Fix | 2025-03-25 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2025-1098US | — | 86.1% (100th) | Exploit | ✗kein Fix | 2025-03-25 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2025-6965US | high7.7 | 73.5% (99th) | Exploit | ✗kein Fix | 2025-07-15 | ≤ vers:unknown/* |
| CVE-2025-24514US | — | 37.3% (99th) | Exploit | ✗kein Fix | 2025-03-25 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2025-1097US | — | 37.0% (99th) | Exploit | ✗kein Fix | 2025-03-25 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-5535US | — | 5.58% (93rd) | Exploit | ✗kein Fix | 2024-06-27 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2022-21658US | medium6.3 | 1.38% (72nd) | Exploit | ✗kein Fix | 2022-01-20 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2023-3446US | medium5.3 | 6.53% (94th) | — | ✗kein Fix | 2023-07-19 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-9143US | — | 5.84% (93rd) | — | ✗kein Fix | 2024-10-16 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2023-5678US | medium5.3 | 4.46% (91st) | — | ✗kein Fix | 2023-11-06 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2023-5363US | high7.5 | 3.94% (90th) | — | ✗kein Fix | 2023-10-25 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2025-24513US | — | 3.33% (89th) | — | ✗kein Fix | 2025-03-25 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-0727US | medium5.5 | 3.19% (88th) | — | ✗kein Fix | 2024-01-26 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2023-3817US | medium5.3 | 3.05% (87th) | — | ✗kein Fix | 2023-07-31 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-30105US | — | 2.94% (87th) | — | ✗kein Fix | 2024-07-09 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-21319US | — | 2.89% (87th) | — | ✗kein Fix | 2024-01-09 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2023-4807US | high7.8 | 1.58% (75th) | — | ✗kein Fix | 2023-09-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2023-7104US | high7.3 | 1.46% (73rd) | — | ✗kein Fix | 2023-12-29 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-0056US | —OT erhöht | 1.18% (68th) | — | ✗kein Fix | 2024-01-09 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-41790US | high7.2 | 0.91% (60th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-41789US | high7.2 | 0.91% (60th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-41788US | high7.2 | 0.91% (60th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-54092US | — | 0.76% (55th) | — | ✓V1.20.2-1 | 2025-04-08 | 4 Versionen |
| CVE-2025-40805US | — | 0.65% (51st) | — | ✓* | 2026-01-13 | 4 Versionen |
| CVE-2024-41794US | critical9.8OT erhöht | 0.63% (50th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2023-2975US | medium5.3 | 0.62% (50th) | — | ✗kein Fix | 2023-07-14 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-23814US | — | 0.62% (50th) | — | ✗kein Fix | 2025-02-11 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-41792US | high7.5 | 0.58% (47th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-41793US | high7.5OT erhöht | 0.55% (46th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| 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-2026-44415DE | critical9.1 | 0.48% (41st) | — | ✗kein Fix | 2026-10-13 | 3 Versionen |
| CVE-2026-44414DE | medium6.8 | 0.47% (40th) | — | ✗kein Fix | 2026-10-13 | 3 Versionen |
| CVE-2025-30280US | — | 0.46% (40th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2025-70873US | — | 0.46% (40th) | — | ✗kein Fix | 2026-03-12 | ≤ vers:unknown/* |
| CVE-2025-40944US | — | 0.44% (38th) | — | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2026-33388US | —OT erhöht | 0.41% (35th) | — | ✗kein Fix | 2026-09-08 | ≤ vers:unknown/* |
| CVE-2025-40898US | — | 0.40% (34th) | — | ✗kein Fix | 2025-12-18 | ≤ vers:unknown/* |
| CVE-2024-41791US | medium6.5OT erhöht | 0.39% (33rd) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-41796US | — | 0.38% (32nd) | — | ✗kein Fix | 2025-04-08 | ≤ vers:unknown/<v1.20.2-1 |
| CVE-2024-0232US | medium5.5 | 0.38% (32nd) | — | ✗kein Fix | 2024-01-16 | ≤ vers:unknown/<v1.20.2-1 |
| 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-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/* |