| CVE-2014-9195US | high7.5OT high | 81.3% (100th) | Exploit | ✗no fix | 2015-01-17 | ≤ vers:RTU500_series_CMU_Firmware/<=11.x |
| CVE-2024-28757US | high7.5 | 2.01% (81st) | Exploit | ✗no fix | 2024-03-10 | ≤ vers:RTU500_series_CMU_Firmware/>=13.7.1|<=13.7.6 |
| CVE-2024-45490US | high7.5 | 1.69% (77th) | Exploit | ✗no fix | 2024-08-30 | ≤ vers:RTU500_series_CMU_Firmware/>=13.7.1|<=13.7.6 |
| CVE-2024-8176US | — | 1.35% (71st) | Exploit | ✗no fix | 2025-03-14 | 5 versions |
| CVE-2025-69421US | high7.5 | 0.94% (61st) | Exploit | ✗no fix | 2026-01-27 | 5 versions |
| CVE-2026-8065US | —OT elevated | 0.49% (42nd) | Exploit | ✗no fix | 2026-09-29 | ≤ vers:RTU500_series_CMU_Firmware/<=11.x |
| CVE-2026-8932US | — | 0.40% (34th) | Exploit | ✗no fix | 2026-07-03 | 4 versions |
| CVE-2010-2965US | high10.0OT high | 57.5% (99th) | — | ✗no fix | 2010-08-05 | ≤ vers:RTU500_series_CMU_Firmware/<=11.x |
| CVE-2020-1968US | low3.7 | 4.90% (92nd) | — | ✗no fix | 2020-09-09 | — |
| CVE-2023-2953US | high7.5 | 2.00% (81st) | — | ✗no fix | 2023-05-30 | 4 versions |
| CVE-2024-45492US | critical9.8 | 1.39% (72nd) | — | ✗no fix | 2024-08-30 | ≤ vers:RTU500_series_CMU_Firmware/>=13.7.1|<=13.7.6 |
| CVE-2025-59375US | — | 1.38% (72nd) | — | ✗no fix | 2025-09-15 | 5 versions |
| CVE-2025-6021US | — | 1.37% (72nd) | — | ✗no fix | 2025-06-12 | 4 versions |
| CVE-2024-45491US | critical9.8 | 1.13% (66th) | — | ✗no fix | 2024-08-30 | ≤ vers:RTU500_series_CMU_Firmware/>=13.7.1|<=13.7.6 |
| CVE-2026-9079US | — | 1.06% (65th) | — | ✗no fix | 2026-07-03 | 4 versions |
| CVE-2022-23937US | high7.5 | 1.03% (64th) | — | ✗no fix | 2022-03-29 | 8 versions |
| CVE-2022-28613US | high7.5 | 0.99% (62nd) | — | ✗no fix | 2022-05-02 | 7 versions |
| CVE-2026-28388US | high7.5 | 0.89% (59th) | — | ✗no fix | 2026-04-07 | 5 versions |
| CVE-2026-8066US | — | 0.74% (54th) | — | ✗no fix | 2026-09-29 | ≤ vers:RTU500_series_CMU_Firmware/<=11.x |
| CVE-2026-11856US | —OT elevated | 0.69% (53rd) | — | ✗no fix | 2026-07-03 | 4 versions |
| CVE-2023-6711US | high7.5 | 0.67% (52nd) | — | ✗no fix | 2023-12-19 | 17 versions |
| CVE-2024-2617US | — | 0.67% (52nd) | — | ✗no fix | 2024-04-30 | 6 versions |
| CVE-2022-2081US | high7.5 | 0.64% (50th) | — | ✗no fix | 2024-01-04 | 7 versions |
| CVE-2026-6732US | high7.5 | 0.63% (50th) | — | ✗no fix | 2026-04-23 | 4 versions |
| CVE-2024-1532US | — | 0.57% (47th) | — | ✗no fix | 2024-03-27 | 17 versions |
| CVE-2026-8927US | —OT elevated | 0.50% (43rd) | — | ✗no fix | 2026-07-03 | 4 versions |
| CVE-2026-1773US | high7.5 | 0.46% (39th) | — | ✗no fix | 2026-02-24 | 10 versions |
| CVE-2024-1531US | — | 0.45% (39th) | — | ✗no fix | 2024-03-27 | 17 versions |
| CVE-2026-17539US | — | 0.37% (30th) | — | ✗no fix | 2026-09-03 | 5 versions |
| CVE-2026-6653US | critical9.8 | 0.36% (29th) | — | ✗no fix | 2026-06-22 | 5 versions |
| CVE-2023-46143US | —OT elevated | 0.33% (26th) | — | ✗no fix | 2023-12-14 | ≤ vers:RTU500_series_CMU_Firmware/<=11.x |
| CVE-2026-6276US | high7.5OT elevated | 0.29% (22nd) | — | ✗no fix | 2026-05-13 | 4 versions |
| CVE-2026-1772US | medium5.3 | 0.29% (22nd) | — | ✗no fix | 2026-02-24 | 10 versions |
| CVE-2025-39203US | — | 0.23% (14th) | — | ✗no fix | 2025-06-24 | 5 versions |
| CVE-2026-8067US | —OT elevated | 0.23% (14th) | — | ✗no fix | 2026-09-29 | ≤ vers:RTU500_series_CMU_Firmware/<=11.x |
| CVE-2026-32777US | medium5.5 | 0.22% (12th) | — | ✗no fix | 2026-03-16 | 5 versions |
| CVE-2026-25210US | high7.8 | 0.21% (11th) | — | ✗no fix | 2026-01-30 | 5 versions |
| CVE-2026-24515US | low2.5 | 0.19% (8th) | — | ✗no fix | 2026-01-23 | 5 versions |
| CVE-2026-32778US | medium5.5 | 0.17% (7th) | — | ✗no fix | 2026-03-16 | 5 versions |
| CVE-2026-8479US | — | 0.17% (6th) | — | ✗no fix | 2026-05-26 | 10 versions |
| CVE-2026-32776US | medium5.5 | 0.17% (6th) | — | ✗no fix | 2026-03-16 | 5 versions |