| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2017-9476 | 2017-07-31 | 2025-04-20 | 6.5 | 3.3 | Unknown |
| CVE-2017-9477 | 2017-07-31 | 2025-04-20 | 6.5 | 3.3 | Unknown |
| CVE-2017-9478 | 2017-07-31 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-9479 | 2017-07-31 | 2025-04-20 | 9.8 | 10.0 | Likely |
| CVE-2017-9480 | 2017-07-31 | 2025-04-20 | 5.5 | 2.1 | Unknown |
| CVE-2017-9481 | 2017-07-31 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-9482 | 2017-07-31 | 2025-04-20 | 9.8 | 10.0 | Likely |
| CVE-2017-9483 | 2017-07-31 | 2025-04-20 | 9.8 | 10.0 | Likely |
| CVE-2017-9484 | 2017-07-31 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-9485 | 2017-07-31 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-9486 | 2017-07-31 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-9487 | 2017-07-31 | 2025-04-20 | 5.9 | 4.3 | Likely |
| CVE-2017-9488 | 2017-07-31 | 2025-04-20 | 8.8 | 5.8 | Unknown |
| CVE-2017-9491 | 2017-07-31 | 2025-04-20 | 5.3 | 5.0 | Likely |
| CVE-2017-9492 | 2017-07-31 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-9521 | 2017-07-31 | 2025-04-20 | 9.8 | 7.5 | Likely |