| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2016-4965 | 2016-09-21 | 2025-04-12 | 8.8 | 9.0 | Likely |
| CVE-2016-4966 | 2016-09-21 | 2025-04-12 | 6.5 | 4.0 | Likely |
| CVE-2016-4967 | 2016-09-21 | 2025-04-12 | 6.5 | 4.0 | Likely |
| CVE-2016-4968 | 2016-09-21 | 2025-04-12 | 6.5 | 4.0 | Likely |
| CVE-2016-4969 | 2016-09-21 | 2025-04-12 | 6.1 | 4.3 | Likely |
| CVE-2021-24009 | 2022-04-06 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2021-26112 | 2022-04-06 | 2024-11-21 | 8.1 | 7.5 | Likely |
| CVE-2021-26114 | 2022-04-06 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2021-32593 | 2022-04-06 | 2024-11-21 | 6.5 | 6.4 | Likely |
| CVE-2021-26113 | 2022-04-06 | 2024-11-21 | 6.2 | 5.0 | Likely |
| CVE-2021-32585 | 2022-04-06 | 2024-11-21 | 7.2 | 4.3 | Likely |
| CVE-2022-33869 | 2023-02-16 | 2024-11-21 | 8.8 | - | - |
| CVE-2023-44251 | 2023-12-13 | 2024-11-21 | 8.3 | - | - |
| CVE-2023-44252 | 2023-12-13 | 2024-11-21 | 8.8 | - | - |
| CVE-2021-26115 | 2024-12-19 | 2025-01-21 | 7.8 | - | - |
| CVE-2021-26102 | 2024-12-19 | 2025-01-21 | 9.8 | - | - |