| CVE-2022-0847US | high7.8OT critical | 92.8% (100th) | KEV | ✗no fix | 2022-03-10 | ≤ vers:unknown/* |
| CVE-2025-6554US | —OT critical | 14.1% (97th) | KEV | ✗no fix | 2025-06-30 | ≤ vers:unknown/* |
| CVE-2025-2783US | —OT critical | 9.24% (95th) | KEV | ✗no fix | 2025-03-26 | ≤ vers:unknown/* |
| CVE-2025-10585US | critical9.8OT critical | 8.97% (95th) | KEV | ✗no fix | 2025-09-24 | ≤ vers:unknown/* |
| CVE-2022-0492US | high7.8OT critical | 5.53% (93rd) | KEV | ✗no fix | 2022-03-03 | ≤ vers:unknown/* |
| CVE-2025-13223US | —OT critical | 4.90% (92nd) | KEV | ✗no fix | 2025-11-17 | ≤ vers:unknown/* |
| CVE-2025-1974US | — | 99.4% (100th) | Exploit | ✗no fix | 2025-03-25 | ≤ vers:unknown/<v225.0update3 |
| CVE-2025-1098US | — | 86.1% (100th) | Exploit | ✗no fix | 2025-03-25 | ≤ vers:unknown/<v225.0update3 |
| CVE-2022-0435US | high8.8 | 67.8% (99th) | Exploit | ✗no fix | 2022-03-25 | ≤ vers:unknown/* |
| CVE-2018-25032US | high7.5 | 51.7% (99th) | Exploit | ✗no fix | 2022-03-25 | ≤ vers:unknown/* |
| CVE-2025-24514US | — | 37.3% (99th) | Exploit | ✗no fix | 2025-03-25 | ≤ vers:unknown/<v225.0update3 |
| CVE-2025-1097US | — | 37.0% (99th) | Exploit | ✗no fix | 2025-03-25 | ≤ vers:unknown/<v225.0update3 |
| 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-2024-5535US | — | 5.58% (93rd) | Exploit | ✗no fix | 2024-06-27 | ≤ vers:unknown/<v225.0update3 |
| CVE-2025-32462US | high8.8OT high | 4.48% (91st) | Exploit | ✗no fix | 2025-06-30 | ≤ vers:unknown/* |
| CVE-2021-38185US | high7.8 | 4.17% (91st) | Exploit | ✗no fix | 2021-08-08 | ≤ vers:unknown/* |
| CVE-2022-23303US | critical9.8 | 3.05% (88th) | Exploit | ✗no fix | 2022-01-17 | ≤ vers:unknown/* |
| CVE-2024-28085US | — | 2.24% (83rd) | Exploit | ✗no fix | 2024-03-27 | ≤ vers:unknown/* |
| CVE-2022-37032US | critical9.1 | 2.21% (83rd) | Exploit | ✗no fix | 2022-09-19 | ≤ vers:unknown/* |
| CVE-2024-6232US | high7.5 | 2.20% (82nd) | Exploit | ✗no fix | 2024-09-03 | ≤ vers:unknown/* |
| CVE-2022-21658US | medium6.3 | 1.38% (72nd) | Exploit | ✗no fix | 2022-01-20 | ≤ vers:unknown/<v225.0update3 |
| CVE-2026-0273US | high7.2 | 1.34% (71st) | Exploit | ✗no fix | 2026-06-10 | ≤ vers:unknown/* |
| CVE-2024-47875US | medium6.1 | 1.13% (66th) | Exploit | ✗no fix | 2024-10-11 | ≤ vers:unknown/* |
| CVE-2024-50602US | — | 1.12% (66th) | Exploit | ✗no fix | 2024-10-27 | ≤ vers:unknown/* |
| CVE-2022-2639US | high7.8 | 0.93% (60th) | Exploit | ✗no fix | 2022-09-01 | ≤ vers:unknown/* |
| CVE-2022-30594US | high7.8OT elevated | 0.80% (56th) | Exploit | ✗no fix | 2022-05-12 | ≤ vers:unknown/* |
| CVE-2025-5222US | — | 0.44% (38th) | Exploit | ✗no fix | 2025-05-27 | ≤ vers:unknown/* |
| CVE-2021-35559US | medium5.0 | 15.9% (97th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2021-35556US | medium5.0 | 8.39% (95th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2017-14919US | high7.5 | 8.30% (95th) | — | ✗no fix | 2017-10-30 | ≤ vers:unknown/* |
| CVE-2019-12900US | critical9.8 | 7.98% (95th) | — | ✗no fix | 2019-06-19 | ≤ vers:unknown/* |
| CVE-2016-9841US | critical9.8 | 7.55% (94th) | — | ✗no fix | 2017-05-23 | ≤ vers:unknown/* |
| CVE-2021-35565US | medium5.0 | 7.40% (94th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2021-35550US | high7.1OT elevated | 7.38% (94th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2021-35561US | medium5.0 | 6.95% (94th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2021-35586US | medium5.0 | 6.79% (94th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2021-35578US | medium5.0 | 6.68% (94th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2023-3446US | medium5.3 | 6.53% (94th) | — | ✗no fix | 2023-07-19 | ≤ vers:unknown/<v225.0update3 |
| CVE-2024-9143US | — | 5.84% (93rd) | — | ✗no fix | 2024-10-16 | ≤ vers:unknown/<v225.0update3 |
| CVE-2021-35564US | medium5.0 | 5.63% (93rd) | — | ✗no fix | 2021-10-20 | ≤ 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-2023-5678US | medium5.3 | 4.46% (91st) | — | ✗no fix | 2023-11-06 | ≤ vers:unknown/<v225.0update3 |
| CVE-2021-35603US | medium4.3 | 4.41% (91st) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2023-5363US | high7.5 | 3.94% (90th) | — | ✗no fix | 2023-10-25 | ≤ vers:unknown/<v225.0update3 |
| CVE-2019-9494US | medium5.9 | 3.88% (90th) | — | ✗no fix | 2019-04-17 | ≤ vers:unknown/* |
| CVE-2021-35588US | low2.6 | 3.87% (90th) | — | ✗no fix | 2021-10-20 | ≤ vers:unknown/* |
| CVE-2019-9495US | low3.7OT elevated | 3.48% (89th) | — | ✗no fix | 2019-04-17 | ≤ vers:unknown/* |