| CVE-2021-44228US | critical10.0OT kritisch | 100.0% (100th) | KEV | ✗kein Fix | 2021-12-10 | ≤ All versions with affected Adaptec RAID |
| CVE-2021-45046US | critical9.0OT kritisch | 100.0% (100th) | KEV | ✗kein Fix | 2021-12-14 | ≤ All versions with affected Adaptec RAID |
| CVE-2020-8694US | medium5.5 | 0.45% (39th) | Exploit | ✓BIOS_V25.02.08 | 2020-11-12 | 2 Versionen |
| CVE-2024-1305US | — | 15.4% (97th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-24974US | high7.5 | 9.76% (96th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-27903US | critical9.8 | 8.92% (95th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-27459US | high7.8 | 8.26% (95th) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v25.02.15 |
| CVE-2022-40982US | medium6.5 | 3.05% (87th) | — | ✓V25.02.14 | 2023-08-11 | 2 Versionen |
| CVE-2024-5594US | — | 0.82% (57th) | — | ✗kein Fix | 2025-01-06 | ≤ vers:unknown/<v25.02.15 |
| CVE-2025-27394US | — | 0.73% (54th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2025-27393US | — | 0.73% (54th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2025-27392US | — | 0.73% (54th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-28882US | — | 0.66% (52nd) | — | ✗kein Fix | 2024-07-08 | ≤ vers:unknown/<v25.02.15 |
| CVE-2025-27395US | medium6.5 | 0.66% (51st) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2023-51438US | critical9.8 | 0.65% (51st) | — | ✓with_maxView_Storage_Manager_V4.14.00.26068_on_Windows | 2024-01-09 | 4 Versionen |
| CVE-2024-42512US | — | 0.60% (49th) | — | ✗kein Fix | 2025-02-10 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-42513US | — | 0.58% (47th) | — | ✗kein Fix | 2025-02-10 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-56336US | — | 0.55% (46th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2020-0543US | medium5.5 | 0.54% (45th) | — | ✓BIOS_V25.02.06 | 2020-06-15 | 2 Versionen |
| CVE-2020-8698US | medium5.5 | 0.52% (44th) | — | ✓BIOS_V25.02.08 | 2020-11-12 | 2 Versionen |
| CVE-2025-27494US | high7.2 | 0.50% (43rd) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-41046US | high7.8 | 0.45% (39th) | — | ✗kein Fix | 2024-07-29 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-52285US | —OT erhöht | 0.45% (39th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2024-4877US | — | 0.44% (38th) | — | ✗kein Fix | 2025-04-03 | ≤ vers:unknown/<v25.02.15 |
| CVE-2025-27396US | — | 0.44% (38th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2020-0590US | high7.8 | 0.42% (37th) | — | ✓BIOS_V25.02.08 | 2020-11-12 | 2 Versionen |
| CVE-2025-27397US | — | 0.41% (35th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2020-24511US | medium6.5OT erhöht | 0.40% (34th) | — | ✓BIOS_V25.02.10 | 2021-06-09 | 2 Versionen |
| CVE-2020-8745US | medium6.8 | 0.38% (32nd) | — | ✓BIOS_V25.02.08 | 2020-11-12 | 2 Versionen |
| CVE-2020-24512US | low3.3OT erhöht | 0.38% (32nd) | — | ✓BIOS_V25.02.10 | 2021-06-09 | 2 Versionen |
| CVE-2021-42060US | high8.2 | 0.35% (29th) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-43323US | high8.2 | 0.35% (29th) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-42059US | medium6.7 | 0.35% (28th) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2020-12357US | medium6.7OT erhöht | 0.35% (28th) | — | ✓BIOS_V25.02.10 | 2021-06-09 | 2 Versionen |
| CVE-2025-27398US | — | 0.34% (27th) | — | ✗kein Fix | 2025-03-11 | ≤ vers:unknown/<v25.02.15 |
| CVE-2020-8703US | medium6.7OT erhöht | 0.33% (26th) | — | ✓BIOS_V25.02.10 | 2021-06-09 | 2 Versionen |
| CVE-2021-33627US | high8.2 | 0.33% (26th) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-42554US | high8.2 | 0.33% (26th) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-45970US | high8.2 | 0.33% (26th) | — | ✗kein Fix | 2022-01-05 | ≤ vers:intdot/<25.02.12 |
| CVE-2020-27339US | medium6.7 | 0.32% (25th) | — | ✗kein Fix | 2021-06-16 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-33625US | high7.5 | 0.32% (24th) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-33626US | high7.8 | 0.31% (24th) | — | ✗kein Fix | 2021-10-01 | ≤ vers:intdot/<25.02.12 |
| CVE-2022-24030US | high7.5 | 0.30% (23rd) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-41841US | high8.2 | 0.30% (23rd) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-41840US | high8.2 | 0.30% (23rd) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-41838US | high8.2 | 0.30% (23rd) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2022-24069US | high8.2 | 0.30% (23rd) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-42113US | high8.2 | 0.30% (22nd) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2021-43615US | high8.2 | 0.29% (22nd) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |
| CVE-2020-5953US | high7.5 | 0.28% (21st) | — | ✗kein Fix | 2022-02-03 | ≤ vers:intdot/<25.02.12 |