| CVE-2024-3596US | critical9.0OT high | 14.9% (97th) | Exploit | ✗no fix | 2024-07-09 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-43485US | — | 3.08% (88th) | — | ✗no fix | 2024-10-08 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-30105US | — | 2.94% (87th) | — | ✗no fix | 2024-07-09 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-43483US | — | 2.90% (87th) | — | ✗no fix | 2024-10-08 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-20672US | — | 2.90% (87th) | — | ✗no fix | 2024-01-09 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-38095US | — | 2.74% (86th) | — | ✗no fix | 2024-07-09 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-35264US | — | 2.56% (85th) | — | ✗no fix | 2024-07-09 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-38081US | — | 1.30% (70th) | — | ✗no fix | 2024-07-09 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-0056US | —OT elevated | 1.18% (68th) | — | ✗no fix | 2024-01-09 | 3 versions |
| CVE-2023-30899US | high8.8 | 1.11% (66th) | — | ✓vers:/_V23.1_HotfixRev1 | 2023-05-09 | 3 versions |
| CVE-2023-30898US | high8.8 | 1.11% (66th) | — | ✓vers:/_V23.1_HotfixRev1 | 2023-05-09 | 3 versions |
| CVE-2025-26389US | critical9.8 | 0.98% (62nd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-52963US | medium5.9 | 0.80% (56th) | — | ✗no fix | 2025-01-14 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-30176US | — | 0.65% (51st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-30175US | — | 0.65% (51st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-30174US | — | 0.65% (51st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-26390US | — | 0.64% (51st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-23815US | —OT elevated | 0.57% (47th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-51444US | — | 0.57% (47th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-51445US | — | 0.55% (46th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2023-45133US | high8.8 | 0.53% (44th) | — | ✗no fix | 2023-10-12 | ≤ vers:unknown/* |
| CVE-2024-51447US | — | 0.48% (42nd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-40566US | critical9.8 | 0.46% (40th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2023-31238US | medium4.8 | 0.43% (37th) | — | ✗no fix | 2023-06-13 | ≤ vers:unknown/* |
| CVE-2025-24009US | — | 0.43% (37th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-32011US | — | 0.42% (36th) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-40815US | —OT elevated | 0.38% (32nd) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2023-30901US | high8.8 | 0.36% (30th) | — | ✗no fix | 2023-06-13 | ≤ vers:unknown/* |
| CVE-2024-51446US | medium5.4 | 0.34% (27th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-24007US | —OT elevated | 0.30% (23rd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-31930US | —OT elevated | 0.29% (21st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-24008US | —OT elevated | 0.27% (20th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-24510US | — | 0.27% (19th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-2884US | — | 0.26% (17th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/* |
| CVE-2025-40556US | — | 0.25% (16th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-40817US | —OT elevated | 0.24% (15th) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-40744US | — | 0.23% (13th) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-40816US | —OT elevated | 0.22% (12th) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-40555US | — | 0.22% (12th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2024-32122US | medium4.4 | 0.22% (12th) | — | ✗no fix | 2025-04-08 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-31929US | — | 0.20% (10th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-32454US | — | 0.18% (8th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/<v23.1 hotfixrev14 |
| CVE-2025-40827US | — | 0.17% (6th) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-40763US | — | 0.15% (4th) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2025-40760US | — | 0.14% (3rd) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2024-32008US | — | 0.13% (3rd) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2024-32010US | — | 0.13% (2nd) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2024-32014US | — | 0.12% (2nd) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |
| CVE-2024-32009US | — | 0.12% (2nd) | — | ✗no fix | 2025-11-11 | ≤ vers:unknown/* |