| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2008-0888 | 2008-03-17 | 2025-05-01 | - | 9.3 | Likely |
| CVE-2014-9636 | 2015-02-06 | 2025-04-12 | - | 5.0 | Likely |
| CVE-2015-7696 | 2015-11-06 | 2025-04-12 | - | 6.8 | Likely |
| CVE-2015-7697 | 2015-11-06 | 2025-04-12 | - | 4.3 | Likely |
| CVE-2014-9913 | 2017-01-18 | 2025-04-20 | 4.0 | 2.1 | Unknown |
| CVE-2016-9844 | 2017-01-18 | 2025-04-20 | 4.0 | 2.1 | Unknown |
| CVE-2018-1000035 | 2018-02-09 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-18384 | 2018-10-16 | 2024-11-21 | 5.5 | 4.3 | Likely |
| CVE-2019-13232 | 2019-07-04 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2014-8139 | 2020-01-31 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2014-8140 | 2020-01-31 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2014-8141 | 2020-01-31 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2022-0529 | 2022-02-09 | 2024-11-21 | 5.5 | 4.3 | Likely |
| CVE-2022-0530 | 2022-02-09 | 2024-11-21 | 5.5 | 4.3 | Likely |
| CVE-2021-4217 | 2022-08-24 | 2024-11-21 | 3.3 | - | - |
| CVE-2020-36561 | 2022-12-27 | 2025-04-11 | 9.1 | - | - |