| CVE-2025-33053US | —OT kritisch | 87.0% (100th) | KEV | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.00|<2.0.505.0 |
| CVE-2025-33073US | —OT kritisch | 82.7% (100th) | KEV | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.00|<2.0.505.0 |
| CVE-2026-33824US | —OT kritisch | 77.1% (100th) | KEV | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-32202US | —OT kritisch | 70.9% (99th) | KEV | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-24054US | medium5.4OT kritisch | 62.3% (99th) | KEV | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-26633US | —OT kritisch | 30.4% (98th) | KEV | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-24985US | —OT kritisch | 3.89% (90th) | KEV | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2026-68820US | —OT kritisch | 0.33% (26th) | KEV | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2025-24993US | —OT kritisch | 2.22% (83rd) | KEV | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-24991US | —OT kritisch | 2.02% (81st) | KEV | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-24984US | —OT kritisch | 1.99% (81st) | KEV | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-24983US | —OT kritisch | 1.87% (79th) | KEV | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-47981US | — | 41.1% (99th) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-24071US | — | 23.3% (98th) | Exploit | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-24076US | — | 3.21% (88th) | Exploit | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-49683US | — | 2.06% (81st) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-47987US | — | 1.79% (78th) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-24035US | — | 1.72% (77th) | Exploit | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2025-49666US | — | 1.42% (73rd) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-48799US | — | 1.26% (69th) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-49677US | — | 1.12% (66th) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-32710US | — | 1.07% (65th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.00|<2.0.505.0 |
| CVE-2026-62878US | — | 0.97% (62nd) | Exploit | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-49179US | — | 0.86% (58th) | Exploit | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-33827US | — | 0.84% (58th) | Exploit | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-49744US | — | 0.81% (57th) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-49730US | — | 0.68% (52nd) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-48804US | — | 0.65% (51st) | Exploit | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2026-33826US | — | 0.53% (45th) | Exploit | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-32223US | — | 0.52% (44th) | Exploit | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-54984US | — | 0.47% (40th) | Exploit | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-26179US | — | 0.44% (38th) | Exploit | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-3052US | — | 0.43% (37th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.00|<2.0.505.0 |
| CVE-2026-27912US | — | 0.41% (35th) | Exploit | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-62737US | — | 0.33% (27th) | Exploit | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-62735US | — | 0.33% (27th) | Exploit | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-66804US | — | 0.30% (22nd) | Exploit | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-25250US | — | 0.12% (2nd) | Exploit | ✗kein Fix | 2026-08-27 | ≤ vers:unknown/* |
| CVE-2025-47984US | — | 23.3% (98th) | — | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-33071US | — | 23.2% (98th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.00|<2.0.505.0 |
| CVE-2025-33070US | — | 9.86% (96th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.00|<2.0.505.0 |
| CVE-2025-49724US | — | 9.81% (96th) | — | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2025-26645US | — | 3.18% (88th) | — | ✓2.0.365.0 | 2025-03-11 | 4 Versionen |
| CVE-2025-21247US | — | 3.05% (88th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/1.00|<2.0.365.0 |
| CVE-2026-27914US | — | 2.43% (84th) | — | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-26169US | — | 2.31% (83rd) | — | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-47978US | — | 2.15% (82nd) | — | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/1.00|<2.0.559.0 |
| CVE-2026-32162US | — | 1.92% (80th) | — | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-32724US | — | 1.82% (79th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.00|<2.0.505.0 |