| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2016-5681 | 2016-08-25 | 2025-04-12 | 9.8 | 9.3 | Likely |
| CVE-2017-14413 | 2017-09-13 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2017-14414 | 2017-09-13 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2017-14415 | 2017-09-13 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2017-14416 | 2017-09-13 | 2025-04-20 | 6.1 | 4.3 | Likely |
| CVE-2017-14417 | 2017-09-13 | 2025-04-20 | 9.8 | 7.5 | Likely |
| CVE-2017-14418 | 2017-09-13 | 2025-04-20 | 8.1 | 4.3 | Likely |
| CVE-2017-14419 | 2017-09-13 | 2025-04-20 | 5.9 | 4.3 | Likely |
| CVE-2017-14420 | 2017-09-13 | 2025-04-20 | 5.9 | 4.3 | Likely |
| CVE-2017-14421 | 2017-09-13 | 2025-04-20 | 9.8 | 10.0 | Likely |
| CVE-2017-14422 | 2017-09-13 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-14423 | 2017-09-13 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-14424 | 2017-09-13 | 2025-04-20 | 7.8 | 2.1 | Unknown |
| CVE-2017-14425 | 2017-09-13 | 2025-04-20 | 7.8 | 2.1 | Unknown |
| CVE-2017-14426 | 2017-09-13 | 2025-04-20 | 7.8 | 2.1 | Unknown |
| CVE-2017-14427 | 2017-09-13 | 2025-04-20 | 7.8 | 2.1 | Unknown |
| CVE-2017-14428 | 2017-09-13 | 2025-04-20 | 7.8 | 2.1 | Unknown |
| CVE-2017-14429 | 2017-09-13 | 2025-05-06 | 9.8 | 10.0 | Likely |
| CVE-2017-14430 | 2017-09-13 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-3193 | 2017-12-16 | 2025-04-20 | 8.8 | 8.3 | Unknown |
| CVE-2018-9032 | 2018-03-27 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2016-6563 | 2018-07-13 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-20674 | 2019-01-09 | 2024-11-21 | 8.8 | 6.5 | Likely |
| CVE-2018-20675 | 2019-01-09 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2019-7642 | 2019-03-25 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2021-46378 | 2022-03-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2021-46379 | 2022-03-04 | 2024-11-21 | 6.1 | 5.8 | Likely |
| CVE-2018-18907 | 2022-06-16 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2023-49004 | 2023-12-19 | 2024-11-21 | 9.8 | - | - |