CVEs
Common Vulnerabilities and Exposures scored on severity, exploitability, and exposure.
243113 cves scored · Page 142 of 2432
critical-risk
762
high-risk
16121
moderate-risk
134619
low-risk
91611
| CVE | Score | Tier |
|---|---|---|
| CVE-2018-0343 | 51/100 | high-risk |
| CVE-2017-11522 | 51/100 | high-risk |
| CVE-2016-7137 | 51/100 | high-risk |
| CVE-2017-11523 | 51/100 | high-risk |
| CVE-2016-7138 | 51/100 | high-risk |
| CVE-2016-7139 | 51/100 | high-risk |
| CVE-2017-1378 | 51/100 | high-risk |
| CVE-2017-13084 | 51/100 | high-risk |
| CVE-2016-7005 | 51/100 | high-risk |
| CVE-2017-9393 | 51/100 | high-risk |
| CVE-2016-6614 | 51/100 | high-risk |
| CVE-2017-13142 | 51/100 | high-risk |
| CVE-2017-13143 | 51/100 | high-risk |
| CVE-2016-2389 | 51/100 | high-risk |
| CVE-2017-8578 | 51/100 | high-risk |
| CVE-2017-8585 | 51/100 | high-risk |
| CVE-2016-4000 | 51/100 | high-risk |
| CVE-2016-9008 | 51/100 | high-risk |
| CVE-2017-1407 | 51/100 | high-risk |
| CVE-2017-13989 | 51/100 | high-risk |
| CVE-2017-0814 | 51/100 | high-risk |
| CVE-2016-1350 | 51/100 | high-risk |
| CVE-2016-8773 | 51/100 | high-risk |
| CVE-2018-0008 | 51/100 | high-risk |
| CVE-2017-18144 | 51/100 | high-risk |
| CVE-2016-1408 | 51/100 | high-risk |
| CVE-2017-18145 | 51/100 | high-risk |
| CVE-2018-0114 | 51/100 | high-risk |
| CVE-2016-10486 | 51/100 | high-risk |
| CVE-2017-9096 | 51/100 | high-risk |
| CVE-2016-0959 | 51/100 | high-risk |
| CVE-2016-5427 | 51/100 | high-risk |
| CVE-2016-6551 | 51/100 | high-risk |
| CVE-2015-8631 | 51/100 | high-risk |
| CVE-2017-9359 | 51/100 | high-risk |
| CVE-2016-10177 | 51/100 | high-risk |
| CVE-2016-1383 | 51/100 | high-risk |
| CVE-2016-10178 | 51/100 | high-risk |
| CVE-2017-9314 | 51/100 | high-risk |
| CVE-2016-6996 | 51/100 | high-risk |
| CVE-2015-8660 | 51/100 | high-risk |
| CVE-2017-14521 | 51/100 | high-risk |
| CVE-2016-10477 | 51/100 | high-risk |
| CVE-2016-7854 | 51/100 | high-risk |
| CVE-2016-10475 | 51/100 | high-risk |
| CVE-2016-6978 | 51/100 | high-risk |
| CVE-2016-6997 | 51/100 | high-risk |
| CVE-2016-3370 | 51/100 | high-risk |
| CVE-2016-7852 | 51/100 | high-risk |
| CVE-2017-14650 | 51/100 | high-risk |
| CVE-2017-6026 | 51/100 | high-risk |
| CVE-2016-3642 | 51/100 | high-risk |
| CVE-2017-14695 | 51/100 | high-risk |
| CVE-2017-12739 | 51/100 | high-risk |
| CVE-2016-5157 | 51/100 | high-risk |
| CVE-2016-10467 | 51/100 | high-risk |
| CVE-2017-12731 | 51/100 | high-risk |
| CVE-2017-5982 | 51/100 | high-risk |
| CVE-2017-10067 | 51/100 | high-risk |
| CVE-2016-4734 | 51/100 | high-risk |
| CVE-2016-7000 | 51/100 | high-risk |
| CVE-2017-16844 | 51/100 | high-risk |
| CVE-2017-5812 | 51/100 | high-risk |
| CVE-2016-6998 | 51/100 | high-risk |
| CVE-2017-11883 | 51/100 | high-risk |
| CVE-2016-1697 | 51/100 | high-risk |
| CVE-2015-8935 | 51/100 | high-risk |
| CVE-2017-16877 | 51/100 | high-risk |
| CVE-2017-15334 | 51/100 | high-risk |
| CVE-2017-11906 | 51/100 | high-risk |
| CVE-2016-0200 | 51/100 | high-risk |
| CVE-2016-7012 | 51/100 | high-risk |
| CVE-2025-29836 | 51/100 | high-risk |
| CVE-2016-6977 | 51/100 | high-risk |
| CVE-2016-7560 | 51/100 | high-risk |
| CVE-2016-5178 | 51/100 | high-risk |
| CVE-2016-0188 | 51/100 | high-risk |
| CVE-2025-29832 | 51/100 | high-risk |
| CVE-2016-6976 | 51/100 | high-risk |
| CVE-2016-6975 | 51/100 | high-risk |
| CVE-2016-7016 | 51/100 | high-risk |
| CVE-2017-10053 | 51/100 | high-risk |
| CVE-2016-5229 | 51/100 | high-risk |
| CVE-2016-7266 | 51/100 | high-risk |
| CVE-2017-15374 | 51/100 | high-risk |
| CVE-2018-0147 | 51/100 | high-risk |
| CVE-2017-2765 | 51/100 | high-risk |
| CVE-2017-1002101 | 51/100 | high-risk |
| CVE-2017-4989 | 51/100 | high-risk |
| CVE-2016-6974 | 51/100 | high-risk |
| CVE-2016-0734 | 51/100 | high-risk |
| CVE-2017-16953 | 51/100 | high-risk |
| CVE-2017-16959 | 51/100 | high-risk |
| CVE-2017-17027 | 51/100 | high-risk |
| CVE-2017-17029 | 51/100 | high-risk |
| CVE-2016-6973 | 51/100 | high-risk |
| CVE-2015-5050 | 51/100 | high-risk |
| CVE-2017-17030 | 51/100 | high-risk |
| CVE-2017-12239 | 51/100 | high-risk |
| CVE-2017-17031 | 51/100 | high-risk |