| CVE-2023-28771US | —OT critical | 99.3% (100th) | KEV | ✗no fix | 2023-04-25 | ≤ 4.60 through 5.35 |
| CVE-2023-33010US | critical9.8OT critical | 29.0% (98th) | KEV | ✗no fix | 2023-05-24 | ≤ 4.50 through 5.36 Patch 1 |
| CVE-2023-33009US | —OT critical | 28.1% (98th) | KEV | ✗no fix | 2023-05-24 | ≤ 4.60 through 5.36 Patch 1 |
| CVE-2024-11667US | critical9.8OT critical | 2.93% (87th) | KEV | ✗no fix | 2024-11-27 | ≤ versions V5.00 through V5.38 |
| CVE-2023-33012US | — | 9.88% (96th) | Exploit | ✗no fix | 2023-07-17 | ≤ 5.00 through 5.36 Patch 2 |
| CVE-2022-0342US | critical9.8 | 95.1% (100th) | — | ✗no fix | 2022-03-28 | ≤ 4.50 through 5.20 |
| CVE-2022-0734US | medium6.1 | 9.40% (95th) | — | ✗no fix | 2022-05-24 | ≤ 4.50 through 5.20 |
| CVE-2022-26531US | high7.8 | 6.17% (93rd) | — | ✗no fix | 2022-05-24 | ≤ 4.50 through 5.21 |
| CVE-2025-9133US | —OT elevated | 5.46% (93rd) | — | ✗no fix | 2025-10-21 | ≤ versions from V4.50 through V5.40 |
| CVE-2022-26532US | high7.8 | 4.83% (92nd) | — | ✗no fix | 2022-05-24 | ≤ 4.50 through 5.21 |
| CVE-2022-38547US | high7.2 | 2.83% (87th) | — | ✗no fix | 2023-02-07 | ≤ 4.50 through 5.32 |
| CVE-2021-35029US | critical9.8 | 2.25% (83rd) | — | ✗no fix | 2021-07-02 | ≤ 4.35 through 5.01 |
| CVE-2023-27991US | high8.8 | 1.45% (73rd) | — | ✗no fix | 2023-04-24 | ≤ 4.50 through 5.35 |
| CVE-2025-11730US | — | 1.45% (73rd) | — | ✗no fix | 2026-02-05 | ≤ versions from V5.35 through V5.41 |
| CVE-2025-8078US | — | 1.45% (73rd) | — | ✗no fix | 2025-10-21 | ≤ version from V4.50 through V5.40 |
| CVE-2024-7203US | — | 1.34% (71st) | — | ✗no fix | 2024-09-03 | ≤ versions V4.60 through V5.38 |
| CVE-2024-42060US | — | 1.34% (71st) | — | ✗no fix | 2024-09-03 | ≤ versions V4.50 through V5.38 |
| CVE-2024-42059US | — | 1.34% (71st) | — | ✗no fix | 2024-09-03 | ≤ versions V5.00 through V5.38 |
| CVE-2023-6398US | — | 1.33% (71st) | — | ✗no fix | 2024-02-20 | ≤ version 4.50 through 5.37 Patch 1 |
| CVE-2024-42057US | — | 1.32% (71st) | — | ✗no fix | 2024-09-03 | ≤ versions V4.50 through V5.38 |
| CVE-2023-22913US | high8.1 | 1.29% (70th) | — | ✗no fix | 2023-04-24 | ≤ 4.50 through 5.35 |
| CVE-2023-22915US | high7.5 | 1.05% (64th) | — | ✗no fix | 2023-04-24 | ≤ 4.50 through 5.35 |
| CVE-2023-22914US | high7.2 | 1.03% (64th) | — | ✗no fix | 2023-04-24 | ≤ 4.50 through 5.35 |
| CVE-2023-6764US | — | 0.89% (59th) | — | ✗no fix | 2024-02-20 | 2 versions |
| CVE-2023-4398US | high7.5 | 0.88% (59th) | — | ✗no fix | 2023-11-28 | ≤ versions 4.50 through 5.37 |
| CVE-2023-22917US | high7.5 | 0.88% (59th) | — | ✗no fix | 2023-04-24 | ≤ 5.00 through 5.32 |
| CVE-2023-22918US | medium6.5 | 0.77% (55th) | — | ✗no fix | 2023-04-24 | ≤ 4.50 through 5.35 |
| CVE-2023-34139US | high8.8 | 0.76% (55th) | — | ✗no fix | 2023-07-17 | ≤ 4.50 through 5.36 Patch 2 |
| CVE-2022-0910US | medium6.5 | 0.73% (54th) | — | ✗no fix | 2022-05-24 | ≤ 4.50 through 5.21 |
| CVE-2023-22916US | high8.1 | 0.69% (53rd) | — | ✗no fix | 2023-04-24 | ≤ 5.00 through 5.35 |
| CVE-2023-34141US | — | 0.68% (52nd) | — | ✗no fix | 2023-07-17 | ≤ 5.00 through 5.36 Patch 2 |
| CVE-2023-34138US | — | 0.68% (52nd) | — | ✗no fix | 2023-07-17 | ≤ 4.60 through 5.36 Patch 2 |
| CVE-2023-6399US | medium6.5 | 0.65% (51st) | — | ✗no fix | 2024-02-20 | ≤ version 4.50 through 5.37 Patch 1 |
| CVE-2024-42058US | — | 0.62% (49th) | — | ✗no fix | 2024-09-03 | ≤ versions V4.50 through V5.38 |
| CVE-2024-6343US | — | 0.60% (49th) | — | ✗no fix | 2024-09-03 | ≤ versions V4.50 through V5.38 |
| CVE-2026-14818US | — | 0.57% (47th) | — | ✗no fix | 2026-08-04 | ≤ from V4.50 through V5.42 Patch 1 |
| CVE-2023-35139US | medium6.1 | 0.46% (40th) | — | ✗no fix | 2023-11-28 | ≤ versions 5.00 through 5.37 |
| CVE-2023-28767US | — | 0.40% (34th) | — | ✗no fix | 2023-07-17 | ≤ 5.00 through 5.36 |
| CVE-2022-40603US | medium6.1 | 0.39% (32nd) | — | ✗no fix | 2022-12-06 | ≤ 4.50 through 5.31 |
| CVE-2023-27990US | medium4.8 | 0.34% (27th) | — | ✗no fix | 2023-04-24 | ≤ 4.50 through 5.35 |
| CVE-2023-33011US | — | 0.34% (27th) | — | ✗no fix | 2023-07-17 | ≤ 5.00 through 5.36 Patch 2 |
| CVE-2024-42061US | — | 0.31% (24th) | — | ✗no fix | 2024-09-03 | ≤ versions V4.50 through V5.38 |
| CVE-2023-6397US | medium5.3 | 0.30% (23rd) | — | ✗no fix | 2024-02-20 | ≤ version 4.50 through 5.37 Patch 1 |
| CVE-2023-34140US | — | 0.30% (23rd) | — | ✗no fix | 2023-07-17 | ≤ 4.50 through 5.36 Patch 2 |
| CVE-2023-35136US | — | 0.24% (15th) | — | ✗no fix | 2023-11-28 | ≤ versions 4.50 through 5.37 |
| CVE-2023-4397US | — | 0.23% (14th) | — | ✗no fix | 2023-11-28 | ≤ 5.37 |
| CVE-2023-37926US | — | 0.22% (13th) | — | ✗no fix | 2023-11-28 | ≤ versions 4.50 through 5.37 |
| CVE-2023-5960US | — | 0.22% (12th) | — | ✗no fix | 2023-11-28 | ≤ versions 4.50 through 5.37 |
| CVE-2023-37925US | — | 0.22% (12th) | — | ✗no fix | 2023-11-28 | ≤ versions 4.50 through 5.37 |
| CVE-2023-5650US | — | 0.21% (12th) | — | ✗no fix | 2023-11-28 | ≤ versions 4.50 through 5.37 |