| CVE-2025-10585US | critical9.8OT critical | 8.97% (95th) | KEV | ✗no fix | 2025-09-24 | ≤ vers:unknown/* |
| CVE-2025-13223US | —OT critical | 4.90% (92nd) | KEV | ✗no fix | 2025-11-17 | ≤ vers:unknown/* |
| CVE-2018-25032US | high7.5 | 51.7% (99th) | Exploit | ✗no fix | 2022-03-25 | ≤ vers:unknown/* |
| CVE-2022-37434US | critical9.8 | 19.2% (97th) | Exploit | ✗no fix | 2022-08-05 | ≤ vers:unknown/* |
| CVE-2025-26465US | medium6.8 | 7.72% (95th) | Exploit | ✗no fix | 2025-02-18 | ≤ vers:unknown/* |
| CVE-2025-32462US | high8.8OT high | 4.48% (91st) | Exploit | ✗no fix | 2025-06-30 | ≤ vers:unknown/* |
| CVE-2022-23303US | critical9.8 | 3.05% (88th) | Exploit | ✗no fix | 2022-01-17 | ≤ vers:unknown/* |
| CVE-2026-0273US | high7.2 | 1.34% (71st) | Exploit | ✗no fix | 2026-06-10 | ≤ vers:unknown/* |
| CVE-2025-5222US | — | 0.44% (38th) | Exploit | ✗no fix | 2025-05-27 | ≤ vers:unknown/* |
| CVE-2024-1305US | — | 15.4% (97th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-24974US | high7.5 | 9.76% (96th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-27903US | critical9.8 | 8.92% (95th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2412.0002 |
| CVE-2017-14919US | high7.5 | 8.30% (95th) | — | ✗no fix | 2017-10-30 | ≤ vers:unknown/* |
| CVE-2024-27459US | high7.8 | 8.26% (95th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2412.0002 |
| CVE-2016-9841US | critical9.8 | 7.55% (94th) | — | ✗no fix | 2017-05-23 | ≤ vers:unknown/* |
| CVE-2005-2096US | high7.5 | 5.63% (93rd) | — | ✗no fix | 2005-07-06 | ≤ vers:unknown/* |
| CVE-2016-9842US | high8.8 | 5.20% (92nd) | — | ✗no fix | 2017-05-23 | ≤ vers:unknown/* |
| CVE-2016-9840US | high8.8 | 4.88% (92nd) | — | ✗no fix | 2017-05-23 | ≤ vers:unknown/* |
| CVE-2019-9494US | medium5.9 | 3.88% (90th) | — | ✗no fix | 2019-04-17 | ≤ vers:unknown/* |
| CVE-2019-9495US | low3.7OT elevated | 3.48% (89th) | — | ✗no fix | 2019-04-17 | ≤ vers:unknown/* |
| CVE-2023-45853US | critical9.8 | 3.45% (89th) | — | ✗no fix | 2023-10-14 | ≤ vers:unknown/* |
| CVE-2022-48174US | critical9.8 | 3.16% (88th) | — | ✗no fix | 2023-08-22 | ≤ vers:unknown/* |
| CVE-2025-9231US | — | 2.24% (83rd) | — | ✗no fix | 2025-09-30 | ≤ vers:unknown/* |
| CVE-2025-9232US | — | 2.00% (81st) | — | ✗no fix | 2025-09-30 | ≤ vers:unknown/* |
| CVE-2022-23304US | critical9.8 | 1.91% (80th) | — | ✗no fix | 2022-01-17 | ≤ vers:unknown/* |
| CVE-2025-9230US | — | 1.55% (75th) | — | ✗no fix | 2025-09-30 | ≤ vers:unknown/* |
| CVE-2026-5121US | — | 1.09% (65th) | — | ✗no fix | 2026-03-30 | ≤ vers:unknown/* |
| CVE-2024-5594US | — | 0.82% (57th) | — | ✗no fix | 2025-01-06 | ≤ vers:unknown/<v2412.0002 |
| CVE-2025-27394US | — | 0.73% (54th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2025-27393US | — | 0.73% (54th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2025-27392US | — | 0.73% (54th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-28882US | — | 0.66% (52nd) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2412.0002 |
| CVE-2025-27395US | medium6.5 | 0.66% (51st) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-42512US | — | 0.60% (48th) | — | ✗no fix | 2025-02-10 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-42513US | — | 0.58% (47th) | — | ✗no fix | 2025-02-10 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-56336US | — | 0.55% (46th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2025-27494US | high7.2 | 0.50% (43rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2026-56451US | — | 0.50% (42nd) | — | ✗no fix | 2026-07-14 | ≤ vers:unknown/* |
| CVE-2025-5914US | high7.8 | 0.47% (41st) | — | ✗no fix | 2025-06-09 | ≤ vers:unknown/* |
| CVE-2024-41046US | high7.8 | 0.45% (39th) | — | ✗no fix | 2024-07-29 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-52285US | —OT elevated | 0.45% (39th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-4877US | — | 0.44% (38th) | — | ✗no fix | 2025-04-03 | ≤ vers:unknown/<v2412.0002 |
| CVE-2025-27396US | — | 0.44% (38th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2026-22184US | high7.8 | 0.41% (35th) | — | ✗no fix | 2026-01-07 | ≤ vers:unknown/* |
| CVE-2025-27397US | — | 0.41% (35th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2022-37660US | —OT elevated | 0.38% (32nd) | — | ✗no fix | 2025-02-11 | ≤ vers:unknown/* |
| CVE-2025-27398US | — | 0.34% (27th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2024-41049US | high7.0 | 0.28% (20th) | — | ✗no fix | 2024-07-29 | ≤ vers:unknown/<v2412.0002 |
| CVE-2025-23384US | — | 0.28% (20th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2412.0002 |
| CVE-2026-7891DE | critical9.1 | 0.27% (20th) | — | ✗no fix | 2026-05-07 | ≤ vers:unknown/* |