| CVE-2025-49704US | —OT kritisch | 100.0% (100th) | KEV | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<16.0.19029.20000 |
| CVE-2025-49706US | —OT kritisch | 99.1% (100th) | KEV | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<16.0.19029.20000 |
| CVE-2026-55040US | —OT kritisch | 69.5% (99th) | KEV | ✗kein Fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2025-30397US | —OT kritisch | 27.3% (98th) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2023-21823US | —OT kritisch | 5.56% (93rd) | KEV | ✓16.0.16130.20156 | 2023-02-14 | 16.0.1 → 16.0.16130.20156 |
| 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/16.0.1|<16.0.18827.20000 |
| CVE-2025-32709US | —OT kritisch | 1.82% (79th) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2026-56164US | critical9.8OT kritisch | 1.01% (63rd) | KEV | ✗kein Fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2026-58644US | —OT kritisch | 15.9% (97th) | KEV | ✗kein Fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2025-32706US | —OT kritisch | 2.33% (83rd) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-32701US | —OT kritisch | 1.42% (73rd) | KEV | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| 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/16.0.1|<16.0.18925.20000 |
| CVE-2026-26114US | — | 3.08% (88th) | Exploit | ✗kein Fix | 2026-03-10 | ≤ vers:unknown/* |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.18925.20000 |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.18925.20000 |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.18925.20000 |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.18925.20000 |
| CVE-2025-29969US | — | 1.16% (67th) | Exploit | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.18925.20000 |
| CVE-2025-29971US | — | 68.1% (99th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| 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/16.0.1|<16.0.18827.20000 |
| 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/16.0.1|<16.0.18925.20000 |
| CVE-2025-29962US | — | 15.6% (97th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-53766US | — | 8.19% (95th) | — | ✓16.0.19127.20000 | 2025-08-12 | 16.0.1 → 16.0.19127.20000 |
| CVE-2025-60724US | — | 6.29% (94th) | — | ✓16.0.19426.20044 | 2025-11-11 | 2 Versionen |
| CVE-2026-40364US | — | 4.42% (91st) | — | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-30388US | — | 4.38% (91st) | — | ✓16.0.18827.20000 | 2025-05-13 | 2 Versionen |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/16.0.1|<16.0.19029.20000 |
| 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-2026-35439US | — | 2.03% (81st) | — | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-29968US | — | 2.02% (81st) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2026-33110US | — | 1.97% (80th) | — | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-40368US | — | 1.82% (79th) | — | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-26677US | — | 1.80% (78th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-47172US | — | 1.75% (78th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.18925.20000 |
| CVE-2026-40357US | — | 1.70% (77th) | — | ✗kein Fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2026-45454US | high8.8 | 1.63% (76th) | — | ✗kein Fix | 2026-06-09 | ≤ vers:unknown/* |
| CVE-2025-29960US | — | 1.53% (75th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-29959US | — | 1.53% (75th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-29954US | — | 1.47% (74th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-29961US | — | 1.44% (73rd) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2025-29958US | — | 1.44% (73rd) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2026-20846US | — | 1.43% (73rd) | — | ✓16.0.19822.20000 | 2026-02-10 | 16.0.1 → 16.0.19822.20000 |
| CVE-2025-29966US | — | 1.43% (73rd) | — | ✗kein Fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.18827.20000 |
| CVE-2026-26106US | — | 1.42% (73rd) | — | ✗kein Fix | 2026-03-10 | ≤ vers:unknown/* |