| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2015-0581 | 2015-01-28 | 2025-04-12 | - | 7.5 | Likely |
| CVE-2015-4190 | 2015-06-17 | 2025-04-12 | - | 4.3 | Likely |
| CVE-2015-6350 | 2015-10-30 | 2025-04-12 | - | 6.5 | Likely |
| CVE-2015-6395 | 2015-12-12 | 2025-04-12 | - | 6.5 | Likely |
| CVE-2016-1462 | 2016-07-28 | 2025-04-12 | 6.1 | 4.3 | Likely |
| CVE-2017-3810 | 2017-02-03 | 2025-04-20 | 5.4 | 4.9 | Unknown |
| CVE-2017-3866 | 2017-03-17 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2017-12364 | 2017-11-30 | 2025-04-20 | 6.5 | 6.4 | Likely |
| CVE-2018-0107 | 2018-01-18 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-0200 | 2018-02-22 | 2024-11-21 | 6.1 | 4.3 | Likely |
| CVE-2018-0285 | 2018-05-02 | 2024-11-21 | 6.5 | 4.0 | Likely |
| CVE-2018-15451 | 2018-11-08 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2019-1874 | 2019-06-20 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-1875 | 2019-06-20 | 2024-11-21 | 4.8 | 3.5 | Unknown |
| CVE-2021-44228 | 2021-12-10 | 2025-04-03 | 10.0 | 9.3 | Likely |
| CVE-2022-20680 | 2022-02-10 | 2024-11-21 | 4.3 | 4.0 | Likely |