CVEs
Common Vulnerabilities and Exposures scored on severity, exploitability, and exposure.
243113 cves scored · Page 143 of 2432
critical-risk
762
high-risk
16121
moderate-risk
134619
low-risk
91611
| CVE | Score | Tier |
|---|---|---|
| CVE-2016-6972 | 51/100 | high-risk |
| CVE-2017-17032 | 51/100 | high-risk |
| CVE-2017-10955 | 51/100 | high-risk |
| CVE-2016-6971 | 51/100 | high-risk |
| CVE-2017-17593 | 51/100 | high-risk |
| CVE-2017-15336 | 51/100 | high-risk |
| CVE-2016-3308 | 51/100 | high-risk |
| CVE-2017-3156 | 51/100 | high-risk |
| CVE-2017-10974 | 51/100 | high-risk |
| CVE-2016-6988 | 51/100 | high-risk |
| CVE-2016-6970 | 51/100 | high-risk |
| CVE-2016-7017 | 51/100 | high-risk |
| CVE-2017-3120 | 51/100 | high-risk |
| CVE-2016-6944 | 51/100 | high-risk |
| CVE-2016-6969 | 51/100 | high-risk |
| CVE-2016-7013 | 51/100 | high-risk |
| CVE-2017-3113 | 51/100 | high-risk |
| CVE-2016-6943 | 51/100 | high-risk |
| CVE-2015-9207 | 51/100 | high-risk |
| CVE-2015-9206 | 51/100 | high-risk |
| CVE-2016-6968 | 51/100 | high-risk |
| CVE-2018-0037 | 51/100 | high-risk |
| CVE-2016-6967 | 51/100 | high-risk |
| CVE-2016-0772 | 51/100 | high-risk |
| CVE-2016-7018 | 51/100 | high-risk |
| CVE-2015-9195 | 51/100 | high-risk |
| CVE-2016-7014 | 51/100 | high-risk |
| CVE-2016-6897 | 51/100 | high-risk |
| CVE-2016-2805 | 51/100 | high-risk |
| CVE-2016-7019 | 51/100 | high-risk |
| CVE-2016-6942 | 51/100 | high-risk |
| CVE-2017-1000484 | 51/100 | high-risk |
| CVE-2016-1840 | 51/100 | high-risk |
| CVE-2016-10431 | 51/100 | high-risk |
| CVE-2016-0072 | 51/100 | high-risk |
| CVE-2015-5007 | 51/100 | high-risk |
| CVE-2017-0260 | 51/100 | high-risk |
| CVE-2017-12620 | 51/100 | high-risk |
| CVE-2016-5270 | 51/100 | high-risk |
| CVE-2016-7880 | 51/100 | high-risk |
| CVE-2017-1000481 | 51/100 | high-risk |
| CVE-2016-6941 | 51/100 | high-risk |
| CVE-2016-2828 | 51/100 | high-risk |
| CVE-2016-6966 | 51/100 | high-risk |
| CVE-2017-17612 | 51/100 | high-risk |
| CVE-2016-2849 | 51/100 | high-risk |
| CVE-2017-17619 | 51/100 | high-risk |
| CVE-2016-1629 | 51/100 | high-risk |
| CVE-2016-9864 | 51/100 | high-risk |
| CVE-2017-17621 | 51/100 | high-risk |
| CVE-2017-1000410 | 51/100 | high-risk |
| CVE-2017-15335 | 51/100 | high-risk |
| CVE-2016-6995 | 51/100 | high-risk |
| CVE-2017-17622 | 51/100 | high-risk |
| CVE-2016-7881 | 51/100 | high-risk |
| CVE-2017-3037 | 51/100 | high-risk |
| CVE-2016-7400 | 51/100 | high-risk |
| CVE-2015-7975 | 51/100 | high-risk |
| CVE-2016-6255 | 51/100 | high-risk |
| CVE-2017-14349 | 51/100 | high-risk |
| CVE-2016-7015 | 51/100 | high-risk |
| CVE-2017-14351 | 51/100 | high-risk |
| CVE-2016-7011 | 51/100 | high-risk |
| CVE-2016-11017 | 51/100 | high-risk |
| CVE-2016-4254 | 51/100 | high-risk |
| CVE-2016-7010 | 51/100 | high-risk |
| CVE-2016-4252 | 51/100 | high-risk |
| CVE-2016-7009 | 51/100 | high-risk |
| CVE-2016-4250 | 51/100 | high-risk |
| CVE-2016-1834 | 51/100 | high-risk |
| CVE-2016-0044 | 51/100 | high-risk |
| CVE-2017-2514 | 51/100 | high-risk |
| CVE-2016-6965 | 51/100 | high-risk |
| CVE-2016-1593 | 51/100 | high-risk |
| CVE-2016-0747 | 51/100 | high-risk |
| CVE-2016-6964 | 51/100 | high-risk |
| CVE-2016-1952 | 51/100 | high-risk |
| CVE-2017-1000170 | 51/100 | high-risk |
| CVE-2016-6963 | 51/100 | high-risk |
| CVE-2016-6940 | 51/100 | high-risk |
| CVE-2016-0024 | 51/100 | high-risk |
| CVE-2016-1953 | 51/100 | high-risk |
| CVE-2016-0012 | 51/100 | high-risk |
| CVE-2016-4616 | 51/100 | high-risk |
| CVE-2016-0376 | 51/100 | high-risk |
| CVE-2016-9814 | 51/100 | high-risk |
| CVE-2025-26482 | 51/100 | high-risk |
| CVE-2017-2364 | 51/100 | high-risk |
| CVE-2017-1000148 | 51/100 | high-risk |
| CVE-2016-4615 | 51/100 | high-risk |
| CVE-2016-4614 | 51/100 | high-risk |
| CVE-2016-2038 | 51/100 | high-risk |
| CVE-2016-3266 | 51/100 | high-risk |
| CVE-2016-0802 | 51/100 | high-risk |
| CVE-2017-2339 | 51/100 | high-risk |
| CVE-2017-2338 | 51/100 | high-risk |
| CVE-2017-2337 | 51/100 | high-risk |
| CVE-2017-2335 | 51/100 | high-risk |
| CVE-2017-17286 | 51/100 | high-risk |
| CVE-2017-3850 | 51/100 | high-risk |