| CVE-2025-49704US | —OT kritisch | 100.0% (100th) | KEV | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1001 |
| CVE-2025-49706US | —OT kritisch | 99.1% (100th) | KEV | ✗kein Fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1001 |
| CVE-2026-32201US | medium6.5OT kritisch | 43.4% (99th) | KEV | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2021-42292US | medium6.8OT kritisch | 43.0% (99th) | KEV | ✓16.0.5239.1001 | 2021-11-10 | 16.0.0.0 → 16.0.5239.1001 |
| 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-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.0.0|<16.0.5504.1000 |
| CVE-2023-33137US | — | 2.75% (86th) | Exploit | ✓16.0.5400.1000 | 2023-06-14 | 16.0.0.0 → 16.0.5400.1000 |
| CVE-2023-23399US | — | 2.53% (85th) | Exploit | ✓16.0.5387.1000 | 2023-03-14 | 16.0.0.0 → 16.0.5387.1000 |
| CVE-2025-27751US | — | 2.48% (85th) | Exploit | ✓16.0.5495.1000 | 2025-04-08 | 16.0.0.0 → 16.0.5495.1000 |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✓16.0.5504.1000 | 2025-06-10 | 2 Versionen |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-53783US | — | 0.81% (57th) | Exploit | ✗kein Fix | 2025-08-12 | ≤ vers:unknown/16.0.0.0|<16.0.5513.1000 |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2023-36041US | high7.8 | 56.7% (99th) | — | ✓16.0.5422.1000 | 2023-11-14 | 16.0.0.0 → 16.0.5422.1000 |
| CVE-2023-32029US | — | 53.5% (99th) | — | ✓16.0.5400.1000 | 2023-06-14 | 16.0.0.0 → 16.0.5400.1000 |
| CVE-2021-34501US | medium6.8 | 51.7% (99th) | — | ✓16.0.5188.100 | 2021-07-14 | 16.0.0.0 → 16.0.5188.100 |
| CVE-2023-33133US | — | 44.0% (99th) | — | ✓16.0.5400.1000 | 2023-06-14 | 16.0.0.0 → 16.0.5400.1000 |
| CVE-2025-47163US | — | 20.9% (98th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-49712US | — | 20.7% (98th) | — | ✗kein Fix | 2025-08-12 | ≤ vers:unknown/16.0.0.0|<16.0.5513.1000 |
| CVE-2026-20945US | medium5.4 | 19.1% (97th) | — | ✗kein Fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-53760US | — | 18.9% (97th) | — | ✗kein Fix | 2025-08-12 | ≤ vers:unknown/16.0.0.0|<16.0.5513.1000 |
| CVE-2026-20947US | — | 18.4% (97th) | — | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2021-31178US | medium4.3 | 16.0% (97th) | — | ✓16.0.5161.1000 | 2021-05-11 | 16.0.0.0 → 16.0.5161.1000 |
| CVE-2021-31179US | medium6.8 | 13.5% (96th) | — | ✓16.0.5161.1000 | 2021-05-11 | 16.0.0.0 → 16.0.5161.1000 |
| CVE-2021-31939US | medium6.8 | 13.3% (96th) | — | ✓16.0.5173.1000 | 2021-06-08 | 16.0.0.0 → 16.0.5173.1000 |
| CVE-2025-53766US | — | 8.19% (95th) | — | ✗kein Fix | 2025-08-12 | ≤ vers:unknown/16.0.0.0|<16.0.5513.1000 |
| CVE-2026-20959US | medium5.4 | 7.68% (95th) | — | ✗kein Fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2024-43504US | — | 6.50% (94th) | — | ✓16.0.5469.1000 | 2024-10-08 | 16.0.0.0 → 16.0.5469.1000 |
| CVE-2021-38655US | medium6.8 | 6.39% (94th) | — | ✓5215.1000 | 2021-09-15 | 16.0.0.0 → 5215.1000 |
| CVE-2020-16932US | medium6.8 | 4.82% (92nd) | — | ✓publication | 2020-10-16 | 16.0.0.0 → publication |
| CVE-2020-16931US | medium6.8 | 4.82% (92nd) | — | ✓publication | 2020-10-16 | 16.0.0.0 → publication |
| CVE-2020-1497US | medium5.5 | 4.64% (92nd) | — | ✓publication | 2020-08-17 | 16.0.0.0 → publication |
| CVE-2022-22716US | medium4.3 | 4.60% (92nd) | — | ✓16.0.5278.1000 | 2022-02-09 | 16.0.0.0 → 16.0.5278.1000 |
| CVE-2021-27053US | medium6.8 | 4.58% (92nd) | — | ✓publication | 2021-03-11 | 16.0.0.0 → publication |
| CVE-2020-1224US | medium4.3 | 4.35% (91st) | — | ✓publication | 2020-09-11 | 16.0.0.0 → publication |
| CVE-2021-27057US | medium6.8 | 4.32% (91st) | — | ✓publication | 2021-03-11 | 16.0.0.0 → publication |
| CVE-2021-27054US | medium6.8 | 4.32% (91st) | — | ✓publication | 2021-03-11 | 16.0.0.0 → publication |
| CVE-2020-1496US | high8.8 | 4.21% (91st) | — | ✓publication | 2020-08-17 | 16.0.0.0 → publication |
| CVE-2020-1495US | high8.8 | 4.21% (91st) | — | ✓publication | 2020-08-17 | 16.0.0.0 → publication |
| CVE-2020-1494US | high8.8 | 4.21% (91st) | — | ✓publication | 2020-08-17 | 16.0.0.0 → publication |
| CVE-2020-17065US | high9.3 | 4.13% (91st) | — | ✓publication | 2020-11-11 | 16.0.0.0 → publication |
| CVE-2026-21511US | — | 3.97% (90th) | — | ✗kein Fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2020-1498US | high8.8 | 3.93% (90th) | — | ✓publication | 2020-08-17 | 16.0.0.0 → publication |
| CVE-2020-1594US | medium6.8 | 3.85% (90th) | — | ✓publication | 2020-09-11 | 16.0.0.0 → publication |
| CVE-2020-1335US | medium6.8 | 3.85% (90th) | — | ✓publication | 2020-09-11 | 16.0.0.0 → publication |
| CVE-2020-1332US | medium6.8 | 3.85% (90th) | — | ✓publication | 2020-09-11 | 16.0.0.0 → publication |