| CVE-2025-49704US | —OT kritisch | 100.0% (100th) | KEV | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/n/a |
| CVE-2025-49706US | —OT kritisch | 99.1% (100th) | KEV | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/n/a |
| CVE-2026-55040US | —OT kritisch | 69.5% (99th) | KEV | ✗kein Fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2026-32201US | medium6.5OT kritisch | 43.4% (99th) | KEV | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-30397US | —OT kritisch | 27.3% (98th) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2026-65660US | high8.8OT kritisch | 8.19% (95th) | KEV | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-50522US | —OT kritisch | 3.04% (87th) | KEV | ✗kein Fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2025-30400US | —OT kritisch | 1.92% (80th) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2025-32709US | —OT kritisch | 1.82% (79th) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2026-21514US | —OT kritisch | 1.59% (75th) | KEV | ✓16.106.26020821 | 2026-02-10 | 2 Versionen |
| CVE-2026-56164US | critical9.8OT kritisch | 1.01% (63rd) | KEV | ✗kein Fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2026-20963US | —OT kritisch | 29.2% (98th) | KEV | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2026-58644US | —OT kritisch | 15.9% (97th) | KEV | ✗kein Fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2026-96951US | high8.8OT kritisch | 9.81% (96th) | KEV | ✗kein Fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2025-32706US | —OT kritisch | 2.33% (83rd) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2025-32701US | —OT kritisch | 1.42% (73rd) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2025-54897US | — | 21.7% (98th) | Exploit | ✗kein Fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-47166US | — | 21.6% (98th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.0.0|<16.98.25060824 |
| CVE-2026-26114US | — | 3.15% (88th) | Exploit | ✗kein Fix | 2026-03-10 | ≤ vers:unknown/* |
| CVE-2025-27751US | — | 2.48% (85th) | Exploit | ✓16.96.25041326 | 2025-04-08 | 16.0.0 → 16.96.25041326 |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✓16.98.25060824 | 2025-06-10 | 2 Versionen |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✓16.98.25060824 | 2025-06-10 | 2 Versionen |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.0.0|<16.98.25060824 |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.0.0|<16.98.25060824 |
| CVE-2025-29969US | — | 1.16% (67th) | Exploit | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2026-63520US | — | 0.96% (61st) | Exploit | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.0.0|<16.98.25060824 |
| CVE-2025-29971US | — | 68.1% (99th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2026-45484US | — | 35.2% (98th) | — | ✗kein Fix | 2026-06-09 | ≤ vers:unknown/* |
| CVE-2025-30394US | — | 34.2% (98th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2026-33112US | — | 31.1% (98th) | — | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-47163US | — | 20.9% (98th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/1.0.0|<16.98.25060824 |
| CVE-2026-20945US | medium5.4 | 19.1% (97th) | — | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-20947US | — | 18.4% (97th) | — | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2025-29962US | — | 15.6% (97th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/1.0.0|<16.97.25042725 |
| CVE-2026-20959US | medium5.4 | 7.68% (95th) | — | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2025-60724US | — | 6.29% (94th) | — | ✓16.103.25110922 | 2025-11-11 | 2 Versionen |
| CVE-2026-40364US | — | 4.42% (91st) | — | ✓16.109.26051019 | 2026-05-12 | 4 Versionen |
| CVE-2025-30388US | — | 4.38% (91st) | — | ✓16.97.25042725 | 2025-05-13 | 2 Versionen |
| CVE-2026-21511US | — | 3.97% (90th) | — | ✓16.106.26020821 | 2026-02-10 | 2 Versionen |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/n/a |
| CVE-2025-59237US | — | 2.46% (84th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-62204US | — | 2.21% (82nd) | — | ✗kein Fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2024-49033US | — | 2.14% (82nd) | — | ✓16.91.24111020 | 2024-11-12 | 1.0.0 → 16.91.24111020 |
| CVE-2026-66808US | — | 2.04% (81st) | — | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-66805US | — | 2.04% (81st) | — | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65663US | — | 2.04% (81st) | — | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65658US | — | 2.04% (81st) | — | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-64901US | — | 2.04% (81st) | — | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-63514US | — | 2.04% (81st) | — | ✗kein Fix | 2026-08-11 | ≤ vers:unknown/* |