| CVE-2025-49704US | —OT critical | 100.0% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/n/a |
| CVE-2025-49706US | —OT critical | 99.1% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/n/a |
| CVE-2026-55040US | —OT critical | 69.5% (99th) | KEV | ✗no fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2026-32201US | medium6.5OT critical | 43.4% (99th) | KEV | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2021-42292US | medium6.8OT critical | 43.0% (99th) | KEV | ✓16.55.21111400 | 2021-11-10 | 16.0.1 → 16.55.21111400 |
| CVE-2025-30397US | —OT critical | 27.3% (98th) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2026-65660US | high8.8OT critical | 8.19% (95th) | KEV | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-50522US | —OT critical | 3.04% (87th) | KEV | ✗no fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2025-30400US | —OT critical | 1.92% (80th) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2025-32709US | —OT critical | 1.82% (79th) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2026-21514US | —OT critical | 1.59% (75th) | KEV | ✓16.106.26020821 | 2026-02-10 | 2 versions |
| CVE-2026-56164US | critical9.8OT critical | 1.01% (63rd) | KEV | ✗no fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2026-20963US | —OT critical | 29.2% (98th) | KEV | ✗no fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2026-58644US | —OT critical | 15.9% (97th) | KEV | ✗no fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2026-96951US | high8.8OT critical | 9.81% (96th) | KEV | ✗no fix | 2026-10-13 | ≤ vers:unknown/* |
| CVE-2025-32706US | —OT critical | 2.33% (83rd) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2025-32701US | —OT critical | 1.42% (73rd) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2023-21716US | critical9.8 | 84.8% (100th) | Exploit | ✓16.70.23021201 | 2023-02-14 | 16.0.1 → 16.70.23021201 |
| CVE-2025-54897US | — | 21.7% (98th) | Exploit | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-47166US | — | 21.6% (98th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.98.25060824 |
| CVE-2026-26114US | — | 3.15% (88th) | Exploit | ✗no fix | 2026-03-10 | ≤ vers:unknown/* |
| CVE-2023-28285US | — | 3.01% (87th) | Exploit | ✓16.72.23040900 | 2023-04-11 | 16.0.1 → 16.72.23040900 |
| CVE-2023-28311US | — | 2.72% (86th) | Exploit | ✓16.72.23040900 | 2023-04-11 | 16.0.1 → 16.72.23040900 |
| CVE-2023-23399US | — | 2.53% (85th) | Exploit | ✓16.71.23031200 | 2023-03-14 | 16.0.1 → 16.71.23031200 |
| CVE-2025-27751US | — | 2.48% (85th) | Exploit | ✓16.96.25041326 | 2025-04-08 | 16.0.1 → 16.96.25041326 |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✓16.98.25060824 | 2025-06-10 | 2 versions |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✓16.98.25060824 | 2025-06-10 | 2 versions |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.98.25060824 |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.98.25060824 |
| CVE-2025-29969US | — | 1.16% (67th) | Exploit | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2026-63520US | — | 0.96% (61st) | Exploit | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.98.25060824 |
| CVE-2025-29971US | — | 68.1% (99th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2023-36041US | high7.8 | 56.7% (99th) | — | ✓16.79.23111019 | 2023-11-14 | 16.0.1 → 16.79.23111019 |
| CVE-2023-32029US | — | 53.5% (99th) | — | ✓16.74.23061100 | 2023-06-14 | 16.0.1 → 16.74.23061100 |
| CVE-2023-33133US | — | 44.0% (99th) | — | ✓16.74.23061100 | 2023-06-14 | 16.0.1 → 16.74.23061100 |
| CVE-2026-45484US | — | 35.2% (98th) | — | ✗no fix | 2026-06-09 | ≤ vers:unknown/* |
| CVE-2025-30394US | — | 34.2% (98th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2026-33112US | — | 31.1% (98th) | — | ✗no fix | 2026-05-12 | ≤ vers:unknown/* |
| CVE-2025-47163US | — | 20.9% (98th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.1|<16.98.25060824 |
| CVE-2026-20945US | medium5.4 | 19.1% (97th) | — | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-20947US | — | 18.4% (97th) | — | ✗no fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2025-29962US | — | 15.6% (97th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.97.25042725 |
| CVE-2026-20959US | medium5.4 | 7.68% (95th) | — | ✗no fix | 2026-01-13 | ≤ vers:unknown/* |
| CVE-2025-60724US | — | 6.29% (94th) | — | ✓16.103.25110922 | 2025-11-11 | 2 versions |
| CVE-2021-43875US | high7.8 | 5.37% (93rd) | — | ✓16.56.21121100 | 2021-12-15 | 16.0.1 → 16.56.21121100 |
| CVE-2022-22716US | medium4.3 | 4.60% (92nd) | — | ✓16.58.22021501 | 2022-02-09 | 16.0.1 → 16.58.22021501 |
| CVE-2026-40364US | — | 4.42% (91st) | — | ✓16.109.26051019 | 2026-05-12 | 4 versions |
| CVE-2025-30388US | — | 4.38% (91st) | — | ✓16.97.25042725 | 2025-05-13 | 2 versions |
| CVE-2026-21511US | — | 3.97% (90th) | — | ✓16.106.26020821 | 2026-02-10 | 2 versions |