| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2015-8227 | 2015-11-24 | 2025-04-12 | - | 8.5 | Unknown |
| CVE-2016-5234 | 2016-06-13 | 2025-04-12 | 8.1 | 9.3 | Likely |
| CVE-2017-15334 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15335 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15336 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15337 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15338 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15339 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15353 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-17166 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17301 | 2018-02-15 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2017-17131 | 2018-03-05 | 2024-11-21 | 5.7 | 6.3 | Unknown |
| CVE-2017-17132 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17133 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-15323 | 2018-03-09 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2017-17251 | 2018-04-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17252 | 2018-04-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17253 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17254 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17255 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17256 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17257 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17258 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17174 | 2018-07-31 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2019-5232 | 2019-11-29 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19415 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19416 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19417 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |