ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
---|---|---|---|---|---|
CVE-2020-25499 | 2020-12-09 | 2024-11-21 | 8.8 | 9.0 | Likely |
CVE-2021-34207 | 2021-08-20 | 2024-11-21 | 6.1 | 4.3 | Likely |
CVE-2021-34215 | 2021-08-20 | 2024-11-21 | 6.1 | 4.3 | Likely |
CVE-2021-34218 | 2021-08-20 | 2024-11-21 | 5.3 | 5.0 | Likely |
CVE-2021-34220 | 2021-08-20 | 2024-11-21 | 6.1 | 4.3 | Likely |
CVE-2021-34223 | 2021-08-20 | 2024-11-21 | 6.1 | 4.3 | Likely |
CVE-2021-34228 | 2021-08-20 | 2024-11-21 | 6.1 | 4.3 | Likely |
CVE-2022-40109 | 2022-09-06 | 2024-11-21 | 9.8 | - | - |
CVE-2022-40110 | 2022-09-06 | 2024-11-21 | 7.5 | - | - |
CVE-2022-40111 | 2022-09-06 | 2024-11-21 | 9.8 | - | - |
CVE-2022-40112 | 2022-09-06 | 2024-11-21 | 7.5 | - | - |
CVE-2024-33820 | 2024-05-01 | 2025-06-17 | 7.5 | - | - |
CVE-2024-42520 | 2024-08-12 | 2024-08-13 | 9.8 | - | - |
CVE-2024-34195 | 2024-08-28 | 2024-08-30 | 9.8 | - | - |
CVE-2024-54907 | 2024-12-26 | 2025-04-09 | 8.8 | - | - |
CVE-2025-25609 | 2025-02-28 | 2025-04-03 | 8.0 | - | - |
CVE-2025-25610 | 2025-02-28 | 2025-04-03 | 8.0 | - | - |
CVE-2025-25635 | 2025-02-28 | 2025-04-03 | 8.0 | - | - |
CVE-2025-25579 | 2025-03-28 | 2025-04-07 | 9.8 | - | - |
CVE-2025-45859 | 2025-05-13 | 2025-06-16 | 5.4 | - | - |
CVE-2025-45864 | 2025-05-13 | 2025-06-17 | 5.4 | - | - |
CVE-2025-45866 | 2025-05-13 | 2025-06-17 | 5.4 | - | - |
CVE-2025-45867 | 2025-05-13 | 2025-06-17 | 5.4 | - | - |
CVE-2025-45858 | 2025-05-13 | 2025-05-23 | 9.8 | - | - |
CVE-2025-45861 | 2025-05-13 | 2025-05-15 | 9.8 | - | - |
CVE-2025-45865 | 2025-05-13 | 2025-05-15 | 9.8 | - | - |
CVE-2025-45863 | 2025-05-13 | 2025-05-23 | 9.8 | - | - |
CVE-2025-4729 | 2025-05-16 | 2025-06-20 | 6.3 | 6.5 | Likely |
CVE-2025-4730 | 2025-05-16 | 2025-06-20 | 8.8 | 9.0 | Likely |
CVE-2025-4731 | 2025-05-16 | 2025-06-20 | 8.8 | 9.0 | Likely |
CVE-2025-4732 | 2025-05-16 | 2025-06-20 | 8.8 | 9.0 | Likely |
CVE-2025-4733 | 2025-05-16 | 2025-06-20 | 8.8 | 9.0 | Likely |
CVE-2025-4823 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4824 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4825 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4826 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4827 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4829 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4830 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4831 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4832 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4833 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4834 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4835 | 2025-05-17 | 2025-05-23 | 8.8 | 9.0 | Likely |
CVE-2025-4852 | 2025-05-18 | 2025-06-04 | 2.4 | 3.3 | Unknown |
CVE-2025-45862 | 2025-05-20 | 2025-05-24 | 6.5 | - | - |
CVE-2025-6149 | 2025-06-17 | 2025-06-23 | 8.8 | 9.0 | Likely |
CVE-2025-6164 | 2025-06-17 | 2025-06-23 | 8.8 | 9.0 | Likely |
CVE-2025-6337 | 2025-06-20 | 2025-08-01 | 8.8 | 9.0 | Likely |
CVE-2025-6393 | 2025-06-21 | 2025-07-09 | 8.8 | 9.0 | Likely |
CVE-2025-6486 | 2025-06-22 | 2025-07-07 | 8.8 | 9.0 | Likely |
CVE-2025-6487 | 2025-06-22 | 2025-07-07 | 8.8 | 9.0 | Likely |