| CVE-2026-21962US | —OT critical | 73.2% (99th) | KEV | ✗no fix | 2026-01-20 | ≤ vers:unknown/* |
| CVE-2025-27363US | high8.1OT critical | 27.8% (98th) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2021-45105US | medium5.9 | 100.0% (100th) | Exploit | ✗no fix | 2021-12-18 | ≤ vers:unknown/* |
| CVE-2022-1471US | critical9.8 | 99.5% (100th) | Exploit | ✗no fix | 2022-12-01 | ≤ vers:unknown/* |
| CVE-2025-66516US | critical9.8 | 89.0% (100th) | Exploit | ✗no fix | 2025-12-04 | ≤ vers:unknown/* |
| CVE-2023-43622US | high7.5 | 68.8% (99th) | Exploit | ✗no fix | 2023-10-23 | ≤ vers:unknown/* |
| CVE-2025-54988US | — | 47.9% (99th) | Exploit | ✗no fix | 2025-08-20 | ≤ vers:unknown/* |
| CVE-2024-38476US | critical9.8 | 41.6% (99th) | Exploit | ✗no fix | 2024-07-01 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2025-48976US | — | 32.9% (98th) | Exploit | ✗no fix | 2025-06-16 | ≤ vers:unknown/* |
| CVE-2025-48924US | — | 2.63% (85th) | Exploit | ✗no fix | 2025-07-11 | ≤ vers:unknown/* |
| CVE-2026-42779US | — | 1.23% (69th) | Exploit | ✗no fix | 2026-05-01 | ≤ vers:unknown/* |
| CVE-2024-50602US | — | 1.12% (66th) | Exploit | ✗no fix | 2024-10-27 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2025-55163US | high7.5 | 1.10% (66th) | Exploit | ✗no fix | 2025-08-13 | ≤ vers:unknown/* |
| CVE-2025-23048US | — | 1.04% (64th) | Exploit | ✗no fix | 2025-07-10 | ≤ vers:unknown/* |
| CVE-2025-54874US | critical9.8 | 0.63% (50th) | Exploit | ✗no fix | 2025-08-05 | ≤ vers:unknown/* |
| CVE-2026-49844US | medium5.9 | 0.60% (48th) | Exploit | ✗no fix | 2026-07-10 | ≤ vers:unknown/* |
| CVE-2025-41249US | —OT elevated | 0.48% (41st) | Exploit | ✗no fix | 2025-09-16 | ≤ vers:unknown/* |
| CVE-2024-52046US | critical9.8 | 24.4% (98th) | — | ✗no fix | 2024-12-25 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2020-13936US | high8.8 | 22.7% (98th) | — | ✗no fix | 2021-03-10 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2020-25649US | high7.5 | 17.7% (97th) | — | ✗no fix | 2020-12-03 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-56337US | — | 8.97% (95th) | — | ✗no fix | 2024-12-20 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-9143US | — | 5.84% (93rd) | — | ✗no fix | 2024-10-16 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2025-5115US | high7.5 | 3.57% (89th) | — | ✗no fix | 2025-08-20 | ≤ vers:unknown/* |
| CVE-2024-47561US | — | 3.26% (88th) | — | ✗no fix | 2024-10-03 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-7254US | high7.5 | 2.77% (86th) | — | ✗no fix | 2024-09-19 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2025-23184US | high7.5 | 2.21% (82nd) | — | ✗no fix | 2025-01-21 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2025-24970US | — | 2.19% (82nd) | — | ✗no fix | 2025-02-10 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-47072US | — | 2.00% (81st) | — | ✗no fix | 2024-11-08 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-11053US | — | 1.97% (80th) | — | ✗no fix | 2024-12-11 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2023-26464US | high7.5 | 1.91% (80th) | — | ✗no fix | 2023-03-10 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-11612US | — | 1.77% (78th) | — | ✗no fix | 2024-11-22 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2025-49796US | — | 1.56% (75th) | — | ✗no fix | 2025-06-16 | ≤ vers:unknown/* |
| CVE-2025-59375US | — | 1.38% (72nd) | — | ✗no fix | 2025-09-15 | ≤ vers:unknown/* |
| CVE-2025-31672US | — | 1.35% (71st) | — | ✗no fix | 2025-04-09 | ≤ vers:unknown/* |
| CVE-2024-47554US | — | 1.31% (71st) | — | ✗no fix | 2024-10-03 | 2 versions |
| CVE-2026-54513US | — | 1.23% (69th) | — | ✗no fix | 2026-06-23 | ≤ vers:unknown/* |
| CVE-2024-40896US | — | 1.22% (68th) | — | ✗no fix | 2024-12-23 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-29857US | — | 1.10% (66th) | — | ✗no fix | 2024-05-14 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2024-28168US | — | 1.04% (64th) | — | ✗no fix | 2024-10-09 | ≤ vers:unknown/12.2.1.4.0 |
| CVE-2025-53864US | — | 0.98% (62nd) | — | ✗no fix | 2025-07-11 | ≤ vers:unknown/* |
| CVE-2024-43204US | — | 0.91% (60th) | — | ✗no fix | 2025-07-10 | ≤ vers:unknown/* |
| CVE-2026-5598US | — | 0.90% (59th) | — | ✗no fix | 2026-04-15 | ≤ vers:unknown/* |
| CVE-2025-7962US | high7.5 | 0.89% (59th) | — | ✗no fix | 2025-07-21 | ≤ vers:unknown/* |
| CVE-2026-54428US | — | 0.87% (59th) | — | ✗no fix | 2026-07-01 | ≤ vers:unknown/* |
| CVE-2025-4949US | medium5.3 | 0.84% (58th) | — | ✗no fix | 2025-05-21 | ≤ vers:unknown/* |
| CVE-2024-42516US | — | 0.82% (57th) | — | ✗no fix | 2025-07-10 | ≤ vers:unknown/* |
| CVE-2024-47252US | — | 0.80% (56th) | — | ✗no fix | 2025-07-10 | ≤ vers:unknown/* |
| CVE-2026-54399US | — | 0.78% (56th) | — | ✗no fix | 2026-07-01 | ≤ vers:unknown/* |
| CVE-2024-41311US | high8.1 | 0.77% (56th) | — | ✗no fix | 2024-10-15 | ≤ vers:unknown/* |
| CVE-2026-4176US | — | 0.74% (54th) | — | ✗no fix | 2026-03-29 | ≤ vers:unknown/* |