| CVE-2025-49704US | —OT critical | 100.0% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2025-49706US | —OT critical | 99.1% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2023-23397US | critical9.8OT critical | 97.2% (100th) | KEV | ✓16.0.5387.1000 | 2023-03-14 | 16.0.0.0 → 16.0.5387.1000 |
| CVE-2026-21514US | —OT critical | 1.59% (75th) | KEV | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2023-35311US | —OT critical | 15.5% (97th) | KEV | ✓16.0.5404.1000 | 2023-07-11 | 16.0.0.0 → 16.0.5404.1000 |
| CVE-2020-16947US | high9.3 | 33.7% (98th) | Exploit | ✓publication | 2020-10-16 | 16.0.0.0 → publication |
| CVE-2025-47166US | — | 21.6% (98th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2024-21378US | — | 11.0% (96th) | Exploit | ✓16.0.5435.1000 | 2024-02-13 | 16.0.0.0 → 16.0.5435.1000 |
| CVE-2020-1493US | medium5.5 | 7.30% (94th) | Exploit | ✓publication | 2020-08-17 | 16.0.0.0 → publication |
| CVE-2023-33131US | — | 5.72% (93rd) | Exploit | ✓16.0.5400.1000 | 2023-06-14 | 16.0.0.0 → 16.0.5400.1000 |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✓16.0.5504.1000 | 2025-06-10 | 2 versions |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2022-35742US | — | 22.3% (98th) | — | ✓16.0.4966.1000 | 2023-06-01 | 16.0.0.0 → 16.0.4966.1000 |
| CVE-2025-47163US | — | 20.9% (98th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2020-1483US | high9.3 | 8.84% (95th) | — | ✓publication | 2020-08-17 | 16.0.0.0 → publication |
| CVE-2019-1200US | high7.8 | 4.65% (92nd) | — | ✓publication | 2019-08-14 | 16.0.0.0 → publication |
| CVE-2019-1204US | medium4.3 | 4.42% (91st) | — | ✓publication | 2019-08-14 | 16.0.0.0 → publication |
| CVE-2020-17119US | medium5.0 | 4.02% (91st) | — | ✓publication | 2020-12-10 | 16.0.0.0 → publication |
| CVE-2026-21511US | — | 3.97% (90th) | — | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2024-30103US | — | 3.42% (89th) | — | ✓16.0.5452.1000 | 2024-06-11 | 16.0.0.0 → 16.0.5452.1000 |
| CVE-2023-33151US | — | 3.40% (89th) | — | ✓16.0.5404.1000 | 2023-07-11 | 16.0.0.0 → 16.0.5404.1000 |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2020-16949US | medium5.0 | 2.97% (87th) | — | ✓publication | 2020-10-16 | 16.0.0.0 → publication |
| CVE-2021-31949US | medium6.8 | 2.57% (85th) | — | ✓16.0.5356.1000. | 2021-06-08 | 16.0.0.0 → 16.0.5356.1000. |
| CVE-2023-36893US | — | 2.19% (82nd) | — | ✓16.0.5408.1000 | 2023-08-08 | 16.0.0.0 → 16.0.5408.1000 |
| CVE-2023-36763US | — | 2.12% (82nd) | — | ✓16.0.5413.1000 | 2023-09-12 | 16.0.0.0 → 16.0.5413.1000 |
| CVE-2024-38020US | — | 1.84% (79th) | — | ✓16.0.5456.1000 | 2024-07-09 | 16.0.0.0 → 16.0.5456.1000 |
| CVE-2025-47172US | — | 1.75% (78th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2026-21260US | — | 1.52% (74th) | — | ✓16.0.5539.1002 | 2026-02-10 | 2 versions |
| CVE-2021-28452US | medium6.8 | 1.29% (70th) | — | ✓publication | 2021-04-13 | 16.0.0.0 → publication |
| CVE-2025-49701US | — | 1.29% (70th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2026-70329US | — | 0.82% (57th) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0.0 → 16.0.5565.1000 |
| CVE-2025-49703US | — | 0.77% (55th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2025-47162US | — | 0.76% (55th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-49695US | — | 0.69% (52nd) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2026-62882US | — | 0.67% (52nd) | — | ✓16.0.5565.1000 | 2026-08-11 | 16.0.0.0 → 16.0.5565.1000 |
| CVE-2025-47167US | — | 0.67% (52nd) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2024-38173US | — | 0.66% (51st) | — | ✓16.0.5461.1001 | 2024-08-13 | 16.0.0.0 → 16.0.5461.1001 |
| CVE-2025-49702US | — | 0.66% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2025-47169US | — | 0.65% (51st) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-47164US | — | 0.65% (51st) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-49698US | — | 0.65% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2025-47170US | — | 0.65% (51st) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2025-49696US | — | 0.64% (50th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0.0|<16.0.5508.1002 |
| CVE-2025-47168US | — | 0.64% (50th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0.0|<16.0.5504.1000 |
| CVE-2026-21261US | — | 0.64% (50th) | — | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |
| CVE-2026-21258US | — | 0.64% (50th) | — | ✗no fix | 2026-02-10 | ≤ vers:unknown/* |