| CVE-2025-53020US | — | 4.96% (92nd) | Exploit | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2023-38709US | — | 3.91% (90th) | Exploit | ✓6.3.0.7 SP 5 | 2024-04-04 | < 6.3.0.7 SP 5 |
| CVE-2006-20001US | high7.5 | 3.55% (89th) | Exploit | ✓6.3.0.7 sp5 | 2023-01-17 | < 6.3.0.7 sp5 |
| CVE-2025-23048US | — | 1.04% (64th) | Exploit | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2025-49812US | — | 0.61% (49th) | Exploit | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2022-32215US | medium6.5 | 70.2% (99th) | — | ✓6.3.0.7 sp5 | 2022-07-14 | < 6.3.0.7 sp5 |
| CVE-2024-24795US | — | 2.87% (87th) | — | ✓6.3.0.7 SP 5 | 2024-04-04 | < 6.3.0.7 SP 5 |
| CVE-2022-21634US | — | 1.75% (78th) | — | ✓6.3.0.7 sp5 | 2022-10-18 | < 6.3.0.7 sp5 |
| CVE-2022-28331US | critical9.8 | 1.57% (75th) | — | ✓6.3.0.7 sp5 | 2023-01-31 | < 6.3.0.7 sp5 |
| CVE-2022-24963US | critical9.8 | 1.47% (74th) | — | ✓6.3.0.7 sp5 | 2023-01-31 | < 6.3.0.7 sp5 |
| CVE-2022-25147US | medium6.5 | 1.42% (73rd) | — | ✓6.3.0.7 sp5 | 2023-01-31 | < 6.3.0.7 sp5 |
| CVE-2025-49630US | — | 1.35% (71st) | — | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2019-4592US | high7.5 | 1.34% (71st) | — | ✗kein Fix | 2020-02-13 | 2 Versionen |
| CVE-2024-43394US | — | 1.27% (70th) | — | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2024-21138US | — | 1.26% (69th) | — | ✗kein Fix | 2024-07-16 | ≤ for Virtual Environments <7.3.7 |
| CVE-2017-1794US | high7.5 | 1.23% (69th) | — | ✗kein Fix | 2018-09-19 | 14 Versionen |
| CVE-2026-66909US | — | 1.15% (67th) | — | ✓6.3.0.7 Service Pack 23 | 2026-08-06 | < 6.3.0.7 Service Pack 23 |
| CVE-2024-21147US | — | 1.14% (66th) | — | ✗kein Fix | 2024-07-16 | ≤ for Virtual Environments <7.3.7 |
| CVE-2025-3357US | — | 1.10% (66th) | — | ✓6.3.0.7-TIV-ITM-SP0020 | 2025-05-28 | 2 Versionen |
| CVE-2024-21144US | low3.7 | 1.06% (64th) | — | ✗kein Fix | 2024-07-16 | ≤ for Virtual Environments <7.3.7 |
| CVE-2024-21131US | — | 1.04% (64th) | — | ✗kein Fix | 2024-07-16 | ≤ for Virtual Environments <7.3.7 |
| CVE-2024-20926US | — | 1.03% (64th) | — | ✗kein Fix | 2024-01-16 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2024-21140US | — | 0.94% (61st) | — | ✗kein Fix | 2024-07-16 | ≤ for Virtual Environments <7.3.7 |
| CVE-2022-21597US | — | 0.93% (61st) | — | ✓6.3.0.7 sp5 | 2022-10-18 | < 6.3.0.7 sp5 |
| CVE-2024-43204US | — | 0.91% (60th) | — | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2024-21145US | medium4.8 | 0.86% (58th) | — | ✗kein Fix | 2024-07-16 | ≤ for Virtual Environments <7.3.7 |
| CVE-2024-20921US | —OT erhöht | 0.86% (58th) | — | ✗kein Fix | 2024-02-17 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2024-21003US | — | 0.86% (58th) | — | ✗kein Fix | 2024-04-16 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2024-21005US | — | 0.85% (58th) | — | ✗kein Fix | 2024-04-16 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2023-38264US | high7.5 | 0.85% (58th) | — | ✗kein Fix | 2024-05-14 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2024-42516US | — | 0.82% (57th) | — | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2024-20919US | — | 0.80% (56th) | — | ✗kein Fix | 2024-02-17 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2024-47252US | — | 0.80% (56th) | — | ✓6.3.0.7 SP 5 | 2025-07-10 | < 6.3.0.7 SP 5 |
| CVE-2024-20932US | — | 0.78% (56th) | — | ✗kein Fix | 2024-01-16 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2026-61466US | — | 0.71% (53rd) | — | ✓6.3.0.7 Service Pack 23 | 2026-08-06 | < 6.3.0.7 Service Pack 23 |
| CVE-2026-57817US | — | 0.69% (53rd) | — | ✓6.3.0.7 Service Pack 23 | 2026-08-06 | < 6.3.0.7 Service Pack 23 |
| CVE-2026-68079US | —OT erhöht | 0.68% (52nd) | — | ✓6.3.0.7 Service Pack 23 | 2026-08-06 | < 6.3.0.7 Service Pack 23 |
| CVE-2026-68481US | — | 0.66% (52nd) | — | ✓6.3.0.7 Service Pack 23 | 2026-08-06 | < 6.3.0.7 Service Pack 23 |
| CVE-2024-20923US | — | 0.60% (49th) | — | ✗kein Fix | 2024-02-17 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2024-21098US | — | 0.57% (47th) | — | ✗kein Fix | 2024-04-16 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2025-3354US | critical9.8 | 0.56% (46th) | — | ✓6.3.0.7-TIV-ITM-SP0021 | 2025-08-06 | 2 Versionen |
| CVE-2025-3320US | critical9.8 | 0.56% (46th) | — | ✓6.3.0.7-TIV-ITM-SP0021 | 2025-08-06 | 2 Versionen |
| CVE-2026-9322US | — | 0.56% (46th) | — | ✓6.3.0.7 Service Pack 23 | 2026-07-30 | < 6.3.0.7 Service Pack 23 |
| CVE-2026-9171US | — | 0.55% (46th) | — | ✓6.3.0.7 Service Pack 23 | 2026-07-17 | < 6.3.0.7 Service Pack 23 |
| CVE-2025-3355US | — | 0.53% (45th) | — | ✗kein Fix | 2025-10-30 | ≤ 6.3.0.7 ≤6.3.0.7 Service Pack 21 |
| CVE-2024-20954US | — | 0.53% (44th) | — | ✗kein Fix | 2024-04-16 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2024-20955US | — | 0.52% (44th) | — | ✗kein Fix | 2024-01-16 | ≤ for Virtual Environments Base <7.3.7 |
| CVE-2026-9330US | — | 0.52% (44th) | — | ✓6.3.0.7 Service Pack 5 | 2026-06-01 | < 6.3.0.7 Service Pack 5 |
| CVE-2026-9311US | — | 0.51% (43rd) | — | ✓6.3.0.7 Service Pack 5 | 2026-06-01 | < 6.3.0.7 Service Pack 5 |
| CVE-2026-4410US | high7.5 | 0.50% (43rd) | — | ✓6.3.0.7 Service Pack 5 | 2026-05-27 | < 6.3.0.7 Service Pack 5 |