| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2005-4499 | 2005-12-22 | 2025-04-03 | - | 7.5 | Likely |
| CVE-2006-3906 | 2006-07-27 | 2025-04-03 | - | 5.0 | Likely |
| CVE-2006-4194 | 2006-08-17 | 2025-04-03 | - | 5.0 | Likely |
| CVE-2006-4312 | 2006-08-23 | 2025-04-03 | - | 6.8 | Unknown |
| CVE-2010-1578 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2010-1579 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2010-1580 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2010-1581 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2010-2814 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2010-2815 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2010-2816 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2010-2817 | 2010-08-09 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2011-0395 | 2011-02-25 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2011-0396 | 2011-02-25 | 2025-04-11 | - | 7.8 | Likely |
| CVE-2016-6366 | 2016-08-18 | 2025-04-12 | 8.8 | 8.5 | Unknown |
| CVE-2016-6367 | 2016-08-18 | 2025-04-12 | 7.8 | 6.8 | Unknown |