| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2016-5984 | 2017-02-01 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2016-6059 | 2017-02-01 | 2025-04-20 | 8.1 | 7.5 | Likely |
| CVE-2016-8999 | 2017-02-01 | 2025-04-20 | 5.4 | 3.5 | Unknown |
| CVE-2016-9000 | 2017-02-01 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2017-1321 | 2017-07-12 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2018-1518 | 2018-10-18 | 2024-11-21 | 6.2 | 2.1 | Unknown |
| CVE-2018-1701 | 2019-02-15 | 2024-11-21 | 8.5 | 6.0 | Unknown |
| CVE-2018-1895 | 2019-02-15 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2018-1875 | 2019-03-05 | 2024-11-21 | 7.4 | 5.8 | Likely |
| CVE-2018-1899 | 2019-03-05 | 2024-11-21 | 4.3 | 3.3 | Unknown |
| CVE-2018-1906 | 2019-04-02 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2018-1917 | 2019-04-02 | 2024-11-21 | 3.5 | 4.0 | Likely |
| CVE-2018-1994 | 2019-04-10 | 2024-11-21 | 6.3 | 7.5 | Likely |
| CVE-2019-4238 | 2019-04-25 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2019-4185 | 2019-06-06 | 2024-11-21 | 8.3 | 5.4 | Unknown |
| CVE-2019-4220 | 2019-06-06 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2019-4257 | 2019-06-06 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2018-1845 | 2019-06-17 | 2024-11-21 | 7.1 | 5.5 | Likely |
| CVE-2019-4237 | 2019-07-01 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2020-4384 | 2020-05-06 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2020-4286 | 2020-05-19 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2020-4298 | 2020-05-19 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2020-4305 | 2020-07-09 | 2024-11-21 | 8.8 | 9.3 | Likely |
| CVE-2022-22454 | 2022-05-10 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2022-22442 | 2022-11-03 | 2025-05-05 | 6.5 | - | - |
| CVE-2022-40752 | 2022-11-16 | 2024-11-21 | 9.8 | - | - |
| CVE-2024-40689 | 2024-07-26 | 2024-11-21 | 6.0 | - | - |
| CVE-2025-1138 | 2025-05-15 | 2025-06-04 | 4.3 | - | - |
| CVE-2025-1499 | 2025-06-01 | 2025-06-09 | 6.5 | - | - |