| CVE-2024-1305US | — | 15.4% (97th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-24974US | high7.5 | 9.76% (96th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-27903US | critical9.8 | 8.92% (95th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-27459US | high7.8 | 8.26% (95th) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-5594US | — | 0.82% (57th) | — | ✗no fix | 2025-01-06 | ≤ vers:unknown/<v2302.0021 |
| CVE-2025-27394US | — | 0.73% (54th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2025-27393US | — | 0.73% (54th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2025-27392US | — | 0.73% (54th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-28882US | — | 0.66% (52nd) | — | ✗no fix | 2024-07-08 | ≤ vers:unknown/<v2302.0021 |
| CVE-2025-27395US | medium6.5 | 0.66% (51st) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-42512US | — | 0.60% (48th) | — | ✗no fix | 2025-02-10 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-42513US | — | 0.58% (47th) | — | ✗no fix | 2025-02-10 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-56336US | — | 0.55% (46th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2025-27494US | high7.2 | 0.50% (43rd) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2023-38075US | high7.8 | 0.47% (40th) | — | ✓V2302.0004 | 2023-09-12 | 2 versions |
| CVE-2023-38074US | — | 0.47% (40th) | — | ✓V2302.0004 | 2023-09-12 | 2 versions |
| CVE-2023-38072US | — | 0.46% (40th) | — | ✓V2302.0004 | 2023-09-12 | 2 versions |
| CVE-2024-41046US | high7.8 | 0.45% (39th) | — | ✗no fix | 2024-07-29 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-52285US | —OT elevated | 0.45% (39th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-4877US | — | 0.44% (38th) | — | ✗no fix | 2025-04-03 | ≤ vers:unknown/<v2302.0021 |
| CVE-2025-27396US | — | 0.44% (38th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2023-38076US | — | 0.44% (38th) | — | ✓V2302.0004 | 2023-09-12 | 2 versions |
| CVE-2023-38071US | high7.8 | 0.43% (37th) | — | ✓V2302.0004 | 2023-09-12 | 2 versions |
| CVE-2023-38070US | — | 0.43% (37th) | — | ✓V2302.0004 | 2023-09-12 | 2 versions |
| CVE-2024-32639US | — | 0.42% (36th) | — | ✓V2302.0011 | 2024-05-14 | 2 versions |
| CVE-2025-27397US | — | 0.41% (35th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2023-38073US | — | 0.40% (34th) | — | ✓V2302.0004 | 2023-09-12 | 2 versions |
| CVE-2025-27398US | — | 0.34% (27th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-23795US | — | 0.32% (25th) | — | ✓V2302.0006 | 2024-02-13 | 4 versions |
| CVE-2024-23798US | — | 0.31% (24th) | — | ✓V2302.0006 | 2024-02-13 | 4 versions |
| CVE-2024-23797US | — | 0.31% (24th) | — | ✓V2302.0006 | 2024-02-13 | 4 versions |
| CVE-2024-23796US | — | 0.31% (24th) | — | ✓V2302.0006 | 2024-02-13 | 4 versions |
| CVE-2024-41049US | high7.0 | 0.28% (20th) | — | ✗no fix | 2024-07-29 | ≤ vers:unknown/<v2302.0021 |
| CVE-2025-23384US | — | 0.28% (20th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-52573US | — | 0.27% (19th) | — | ✓V2302.0018 | 2024-11-18 | 2 versions |
| CVE-2024-52569US | — | 0.27% (19th) | — | ✓V2302.0018 | 2024-11-18 | 2 versions |
| CVE-2024-52567US | — | 0.27% (19th) | — | ✓V2302.0018 | 2024-11-18 | 2 versions |
| CVE-2023-37246US | high7.8 | 0.27% (18th) | — | ✓V2302.0002 | 2023-07-11 | 2 versions |
| CVE-2024-45463US | high7.8 | 0.26% (18th) | — | ✓V2302.0016 | 2024-10-08 | 3 versions |
| CVE-2024-42154US | medium4.4 | 0.26% (18th) | — | ✗no fix | 2024-07-30 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-41055US | medium5.5 | 0.26% (17th) | — | ✗no fix | 2024-07-29 | ≤ vers:unknown/<v2302.0021 |
| CVE-2024-45471US | high7.8 | 0.25% (17th) | — | ✓V2302.0016 | 2024-10-08 | 3 versions |
| CVE-2024-45469US | high7.8 | 0.25% (17th) | — | ✓V2302.0016 | 2024-10-08 | 3 versions |
| CVE-2024-35303US | — | 0.25% (16th) | — | ✓V2302.0012 | 2024-06-11 | 2 versions |
| CVE-2023-45601US | high7.8 | 0.25% (16th) | — | ✓V2302.0003 | 2023-10-10 | 3 versions |
| CVE-2024-45470US | high7.8 | 0.24% (16th) | — | ✓V2302.0016 | 2024-10-08 | 3 versions |
| CVE-2024-45466US | high7.8 | 0.24% (16th) | — | ✓V2302.0016 | 2024-10-08 | 3 versions |
| CVE-2024-45465US | high7.8 | 0.24% (16th) | — | ✓V2302.0016 | 2024-10-08 | 3 versions |
| CVE-2024-45464US | high7.8 | 0.24% (16th) | — | ✓V2302.0016 | 2024-10-08 | 3 versions |
| CVE-2023-45204US | high7.8 | 0.24% (16th) | — | ✓V2302.0003 | 2023-10-10 | 3 versions |