| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2016-8757 | 2017-04-02 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2016-8759 | 2017-04-02 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2016-8760 | 2017-04-02 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2016-8761 | 2017-04-02 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2016-8762 | 2017-04-02 | 2025-04-20 | 5.0 | 1.9 | Unknown |
| CVE-2016-8763 | 2017-04-02 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2016-8764 | 2017-04-02 | 2025-04-20 | 6.4 | 4.1 | Unknown |
| CVE-2016-8774 | 2017-04-02 | 2025-04-20 | 6.7 | 7.2 | Unknown |
| CVE-2016-8776 | 2017-04-02 | 2025-04-20 | 4.6 | 2.1 | Unknown |
| CVE-2017-2691 | 2017-11-22 | 2025-04-20 | 6.8 | 7.2 | Unknown |
| CVE-2017-2703 | 2017-11-22 | 2025-04-20 | 6.8 | 7.2 | Unknown |
| CVE-2017-2705 | 2017-11-22 | 2025-04-20 | 2.4 | 2.1 | Unknown |
| CVE-2017-2713 | 2017-11-22 | 2025-04-20 | 5.4 | 4.8 | Unknown |
| CVE-2017-2727 | 2017-11-22 | 2025-04-20 | 4.3 | 4.6 | Unknown |
| CVE-2017-8148 | 2017-11-22 | 2025-04-20 | 4.7 | 5.4 | Unknown |
| CVE-2017-8150 | 2017-11-22 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-8214 | 2017-11-22 | 2025-04-20 | 6.2 | 7.2 | Unknown |
| CVE-2017-8215 | 2017-11-22 | 2025-04-20 | 6.2 | 7.2 | Unknown |
| CVE-2017-17319 | 2018-03-20 | 2024-11-21 | 5.5 | 7.1 | Likely |
| CVE-2017-17171 | 2018-06-01 | 2024-11-21 | 4.2 | 6.3 | Unknown |