| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2012-3271 | 2012-11-29 | 2025-04-11 | - | 9.3 | Likely |
| CVE-2013-2338 | 2013-06-14 | 2025-04-11 | - | 10.0 | Likely |
| CVE-2014-7876 | 2015-03-31 | 2025-04-12 | - | 10.0 | Likely |
| CVE-2015-2106 | 2015-03-31 | 2025-04-12 | - | 6.4 | Likely |
| CVE-2015-5435 | 2015-09-30 | 2025-04-12 | - | 4.0 | Likely |
| CVE-2016-4375 | 2016-09-08 | 2025-04-12 | 9.8 | 7.5 | Likely |
| CVE-2017-12542 | 2018-02-15 | 2024-11-21 | 10.0 | 10.0 | Likely |
| CVE-2017-12543 | 2018-02-15 | 2024-11-21 | 6.5 | 4.0 | Likely |
| CVE-2016-4406 | 2018-08-06 | 2024-11-21 | 6.1 | 4.3 | Likely |
| CVE-2018-7078 | 2018-08-06 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2018-7093 | 2018-08-14 | 2024-11-21 | 8.6 | 7.8 | Likely |
| CVE-2018-7101 | 2018-09-27 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2018-7105 | 2018-09-27 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2018-7112 | 2018-12-03 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2019-11982 | 2019-06-05 | 2024-11-21 | 8.3 | 7.6 | Unknown |
| CVE-2019-11983 | 2019-06-05 | 2024-11-21 | 7.0 | 8.3 | Likely |