| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2015-8307 | 2016-04-07 | 2025-04-12 | 7.8 | 9.3 | Likely |
| CVE-2015-8318 | 2016-04-07 | 2025-04-12 | 7.8 | 9.3 | Likely |
| CVE-2015-8319 | 2016-04-07 | 2025-04-12 | 7.8 | 9.3 | Likely |
| CVE-2015-8679 | 2016-04-07 | 2025-04-12 | 5.5 | 7.1 | Likely |
| CVE-2015-8680 | 2016-04-07 | 2025-04-12 | 7.8 | 9.3 | Likely |
| CVE-2015-8681 | 2016-04-07 | 2025-04-12 | 7.8 | 9.3 | Likely |
| CVE-2015-8682 | 2016-04-13 | 2025-04-12 | 6.1 | 7.8 | Likely |
| CVE-2016-1495 | 2016-04-13 | 2025-04-12 | 7.8 | 9.3 | Likely |
| CVE-2016-8279 | 2016-09-26 | 2025-04-12 | 5.5 | 7.1 | Likely |
| CVE-2015-8678 | 2017-03-24 | 2025-04-20 | 5.5 | 7.1 | Likely |
| CVE-2016-8774 | 2017-04-02 | 2025-04-20 | 6.7 | 7.2 | Unknown |
| CVE-2016-8791 | 2017-04-02 | 2025-04-20 | 7.1 | 6.2 | Unknown |
| CVE-2016-8792 | 2017-04-02 | 2025-04-20 | 7.1 | 6.2 | Unknown |
| CVE-2016-8793 | 2017-04-02 | 2025-04-20 | 6.7 | 6.2 | Unknown |
| CVE-2016-8794 | 2017-04-02 | 2025-04-20 | 7.1 | 6.2 | Unknown |
| CVE-2017-2692 | 2017-11-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-2693 | 2017-11-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-2699 | 2017-11-22 | 2025-04-20 | 7.8 | 6.8 | Likely |