| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2022-26438 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-26439 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-26440 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-26441 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-26442 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-26443 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-26444 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-26445 | 2022-08-01 | 2024-11-21 | 6.7 | - | - |
| CVE-2022-32657 | 2023-01-03 | 2025-04-10 | 6.7 | - | - |
| CVE-2022-32658 | 2023-01-03 | 2025-04-10 | 6.7 | - | - |
| CVE-2022-32659 | 2023-01-03 | 2025-04-10 | 6.7 | - | - |
| CVE-2022-32654 | 2023-02-06 | 2025-03-26 | 6.7 | - | - |
| CVE-2022-32655 | 2023-02-06 | 2025-03-26 | 6.7 | - | - |
| CVE-2022-32656 | 2023-02-06 | 2025-03-26 | 6.7 | - | - |
| CVE-2022-32663 | 2023-02-06 | 2025-03-26 | 7.5 | - | - |
| CVE-2022-32666 | 2023-07-04 | 2024-11-21 | 7.5 | - | - |