| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2016-1521 | 2016-02-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-1522 | 2016-02-13 | 2025-04-12 | 8.8 | 9.3 | Likely |
| CVE-2016-1523 | 2016-02-13 | 2025-04-12 | 6.5 | 4.3 | Likely |
| CVE-2016-1526 | 2016-02-13 | 2025-04-12 | 8.1 | 5.8 | Likely |
| CVE-2016-1969 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-1977 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2790 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2791 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2792 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2793 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2794 | 2016-03-13 | 2025-04-12 | 8.8 | 9.3 | Likely |
| CVE-2016-2795 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2796 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2797 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2798 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2799 | 2016-03-13 | 2025-04-12 | 8.8 | 9.3 | Likely |
| CVE-2016-2800 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2801 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-2802 | 2016-03-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2018-7999 | 2018-03-09 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2017-5436 | 2018-06-11 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2017-7778 | 2018-06-11 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2017-7772 | 2019-04-12 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2017-7771 | 2019-04-15 | 2024-11-21 | 8.1 | 5.8 | Likely |
| CVE-2017-7773 | 2019-04-15 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2017-7774 | 2019-04-15 | 2024-11-21 | 9.1 | 6.4 | Likely |
| CVE-2017-7776 | 2019-04-15 | 2024-11-21 | 8.1 | 5.8 | Likely |
| CVE-2017-7777 | 2019-04-15 | 2024-11-21 | 8.8 | 6.8 | Likely |