| CVE-2025-49704US | —OT kritisch | 100.0% (100th) | KEV | ✗kein Fix | 2025-07-08 | 2 Versionen |
| CVE-2025-49706US | —OT kritisch | 99.1% (100th) | KEV | ✗kein Fix | 2025-07-08 | 2 Versionen |
| CVE-2026-21514US | —OT kritisch | 1.59% (75th) | KEV | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-20963US | —OT kritisch | 29.2% (98th) | KEV | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2023-36761US | medium6.5OT kritisch | 19.6% (97th) | KEV | ✓16.0.5413.1000 | 2023-09-12 | 16.0.1 → 16.0.5413.1000 |
| CVE-2023-21716US | critical9.8 | 84.8% (100th) | Exploit | ✓16.0.5383.1000 | 2023-02-14 | 16.0.1 → 16.0.5383.1000 |
| 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.5504.1000 |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.5504.1000 |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.5504.1000 |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.5504.1000 |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.5504.1000 |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.5504.1000 |
| CVE-2025-47163US | — | 20.9% (98th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.5504.1000 |
| CVE-2026-20947US | — | 18.4% (97th) | — | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2026-20959US | medium5.4 | 7.68% (95th) | — | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2021-40486US | medium6.8 | 5.99% (93rd) | — | ✓16.0.5227.1000 | 2021-10-13 | 16.0.1 → 16.0.5227.1000 |
| CVE-2020-1583US | medium4.3 | 4.91% (92nd) | — | ✓publication | 2020-08-17 | 16.0.1 → publication |
| CVE-2019-1034US | high7.8 | 4.88% (92nd) | — | ✓publication | 2019-06-12 | 16.0.1 → publication |
| CVE-2019-1201US | high7.8 | 4.86% (92nd) | — | ✓publication | 2019-08-14 | 16.0.1 → publication |
| CVE-2020-1503US | medium5.5 | 4.55% (92nd) | — | ✓publication | 2020-08-17 | 16.0.1 → publication |
| CVE-2026-40364US | — | 4.42% (91st) | — | ✓16.0.5552.1000 | 2026-05-12 | 16.0.1 → 16.0.5552.1000 |
| CVE-2021-28453US | medium6.8 | 4.05% (91st) | — | ✓publication | 2021-04-13 | 16.0.1 → publication |
| CVE-2026-21511US | — | 3.97% (90th) | — | ✓16.0.5539.1002 | 2026-02-10 | 2 Versionen |
| CVE-2021-1716US | high9.3 | 3.89% (90th) | — | ✓publication | 2021-01-12 | 16.0.1 → publication |
| CVE-2021-1715US | high9.3 | 3.89% (90th) | — | ✓publication | 2021-01-12 | 16.0.1 → publication |
| CVE-2020-1218US | medium6.8 | 3.83% (90th) | — | ✓publication | 2020-09-11 | 16.0.1 → publication |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✗kein Fix | 2025-07-08 | 2 Versionen |
| CVE-2022-29107US | medium5.5 | 3.06% (88th) | — | ✓16.0.5317.1000 | 2022-05-10 | 16.0.1 → 16.0.5317.1000 |
| CVE-2020-16933US | medium6.8 | 2.74% (86th) | — | ✓publication | 2020-10-16 | 16.0.1 → publication |
| CVE-2025-59237US | — | 2.46% (84th) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2021-31180US | medium6.8 | 2.34% (84th) | — | ✓publication | 2021-05-11 | 16.0.1 → publication |
| CVE-2021-34452US | medium6.8 | 2.33% (83rd) | — | ✓16.0.5188.1000 | 2021-07-16 | 16.0.1 → 16.0.5188.1000 |
| CVE-2022-21842US | medium6.8 | 2.27% (83rd) | — | ✓16.0.5266.1000 | 2022-01-11 | 16.0.1 → 16.0.5266.1000 |
| CVE-2023-33150US | — | 2.15% (82nd) | — | ✓16.0.5404.1000 | 2023-07-11 | 16.0.1 → 16.0.5404.1000 |
| CVE-2024-49033US | — | 2.14% (82nd) | — | ✓16.0.5474.1000 | 2024-11-12 | 16.0.1 → 16.0.5474.1000 |
| CVE-2025-47172US | — | 1.75% (78th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.0.5504.1000 |
| CVE-2024-21379US | — | 1.72% (77th) | — | ✓16.0.5435.1000 | 2024-02-13 | 16.0.1 → 16.0.5435.1000 |
| CVE-2026-21260US | — | 1.52% (74th) | — | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2025-59228US | — | 1.36% (72nd) | — | ✗kein Fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-49701US | — | 1.29% (70th) | — | ✗kein Fix | 2025-07-08 | 2 Versionen |
| CVE-2020-17020US | low2.1 | 1.26% (69th) | — | ✓publication | 2020-11-11 | 16.0.1 → publication |
| CVE-2022-41061US | — | 1.21% (68th) | — | ✓16.0.5369.1000 | 2022-11-09 | 16.0.1 → 16.0.5369.1000 |
| CVE-2024-20673US | — | 1.18% (67th) | — | ✓16.0.5435.1000 | 2024-02-13 | 16.0.1 → 16.0.5435.1000 |
| CVE-2023-29335US | — | 1.16% (67th) | — | ✓16.0.5395.1000 | 2023-05-09 | 16.0.1 → 16.0.5395.1000 |
| CVE-2025-55243US | — | 1.16% (67th) | — | ✗kein Fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2024-49065US | — | 1.10% (66th) | — | ✓16.0.5478.1000 | 2024-12-12 | 16.0.1 → 16.0.5478.1000 |
| CVE-2022-24511US | low1.9 | 1.09% (65th) | — | ✓16.0.5290.1000 | 2022-03-09 | 16.0.1 → 16.0.5290.1000 |
| CVE-2025-26630US | — | 0.97% (62nd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<16.0.18526.20080 |
| CVE-2025-24057US | — | 0.97% (62nd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/16.0.1|<16.0.18526.20080 |