CVEs
Common Vulnerabilities and Exposures scored on severity, exploitability, and exposure.
243113 cves scored · Page 153 of 2432
critical-risk
762
high-risk
16121
moderate-risk
134619
low-risk
91611
| CVE | Score | Tier |
|---|---|---|
| CVE-2017-2171 | 50/100 | high-risk |
| CVE-2016-4221 | 50/100 | high-risk |
| CVE-2016-4220 | 50/100 | high-risk |
| CVE-2016-4219 | 50/100 | high-risk |
| CVE-2016-4218 | 50/100 | high-risk |
| CVE-2017-7651 | 50/100 | high-risk |
| CVE-2017-7680 | 50/100 | high-risk |
| CVE-2017-7681 | 50/100 | high-risk |
| CVE-2017-7684 | 50/100 | high-risk |
| CVE-2016-9700 | 50/100 | high-risk |
| CVE-2016-4202 | 50/100 | high-risk |
| CVE-2016-1037 | 50/100 | high-risk |
| CVE-2016-4195 | 50/100 | high-risk |
| CVE-2016-7873 | 50/100 | high-risk |
| CVE-2016-7874 | 50/100 | high-risk |
| CVE-2016-4190 | 50/100 | high-risk |
| CVE-2016-1063 | 50/100 | high-risk |
| CVE-2016-4189 | 50/100 | high-risk |
| CVE-2016-4187 | 50/100 | high-risk |
| CVE-2017-7746 | 50/100 | high-risk |
| CVE-2017-7747 | 50/100 | high-risk |
| CVE-2016-1071 | 50/100 | high-risk |
| CVE-2016-1072 | 50/100 | high-risk |
| CVE-2016-1073 | 50/100 | high-risk |
| CVE-2016-1074 | 50/100 | high-risk |
| CVE-2016-1076 | 50/100 | high-risk |
| CVE-2016-1078 | 50/100 | high-risk |
| CVE-2016-1080 | 50/100 | high-risk |
| CVE-2016-4186 | 50/100 | high-risk |
| CVE-2016-4184 | 50/100 | high-risk |
| CVE-2016-4183 | 50/100 | high-risk |
| CVE-2016-1095 | 50/100 | high-risk |
| CVE-2025-26794 | 50/100 | high-risk |
| CVE-2016-4181 | 50/100 | high-risk |
| CVE-2016-4180 | 50/100 | high-risk |
| CVE-2017-7807 | 50/100 | high-risk |
| CVE-2017-17417 | 50/100 | high-risk |
| CVE-2016-1112 | 50/100 | high-risk |
| CVE-2016-4172 | 50/100 | high-risk |
| CVE-2016-4166 | 50/100 | high-risk |
| CVE-2016-9578 | 50/100 | high-risk |
| CVE-2017-1696 | 50/100 | high-risk |
| CVE-2016-3219 | 50/100 | high-risk |
| CVE-2017-16388 | 50/100 | high-risk |
| CVE-2017-1189 | 50/100 | high-risk |
| CVE-2016-1757 | 50/100 | high-risk |
| CVE-2017-12934 | 50/100 | high-risk |
| CVE-2017-16389 | 50/100 | high-risk |
| CVE-2017-7989 | 50/100 | high-risk |
| CVE-2016-7191 | 50/100 | high-risk |
| CVE-2017-8022 | 50/100 | high-risk |
| CVE-2017-8032 | 50/100 | high-risk |
| CVE-2016-9449 | 50/100 | high-risk |
| CVE-2016-9447 | 50/100 | high-risk |
| CVE-2016-9427 | 50/100 | high-risk |
| CVE-2017-0243 | 50/100 | high-risk |
| CVE-2016-9382 | 50/100 | high-risk |
| CVE-2016-10708 | 50/100 | high-risk |
| CVE-2017-8274 | 50/100 | high-risk |
| CVE-2017-12945 | 50/100 | high-risk |
| CVE-2017-18781 | 50/100 | high-risk |
| CVE-2015-9137 | 50/100 | high-risk |
| CVE-2015-9124 | 50/100 | high-risk |
| CVE-2025-41697 | 50/100 | high-risk |
| CVE-2017-16390 | 50/100 | high-risk |
| CVE-2015-9119 | 50/100 | high-risk |
| CVE-2015-9118 | 50/100 | high-risk |
| CVE-2017-16393 | 50/100 | high-risk |
| CVE-2017-8479 | 50/100 | high-risk |
| CVE-2016-1244 | 50/100 | high-risk |
| CVE-2016-1256 | 50/100 | high-risk |
| CVE-2016-1258 | 50/100 | high-risk |
| CVE-2016-1261 | 50/100 | high-risk |
| CVE-2017-8488 | 50/100 | high-risk |
| CVE-2016-5313 | 50/100 | high-risk |
| CVE-2017-8489 | 50/100 | high-risk |
| CVE-2017-8491 | 50/100 | high-risk |
| CVE-2015-8833 | 50/100 | high-risk |
| CVE-2025-26682 | 50/100 | high-risk |
| CVE-2017-0167 | 50/100 | high-risk |
| CVE-2015-8821 | 50/100 | high-risk |
| CVE-2017-8506 | 50/100 | high-risk |
| CVE-2017-8507 | 50/100 | high-risk |
| CVE-2015-8812 | 50/100 | high-risk |
| CVE-2016-1283 | 50/100 | high-risk |
| CVE-2017-8534 | 50/100 | high-risk |
| CVE-2015-1836 | 50/100 | high-risk |
| CVE-2016-7136 | 50/100 | high-risk |
| CVE-2016-6922 | 50/100 | high-risk |
| CVE-2018-0345 | 50/100 | high-risk |
| CVE-2017-13098 | 50/100 | high-risk |
| CVE-2015-8769 | 50/100 | high-risk |
| CVE-2016-6455 | 50/100 | high-risk |
| CVE-2016-2403 | 50/100 | high-risk |
| CVE-2016-2396 | 50/100 | high-risk |
| CVE-2017-8588 | 50/100 | high-risk |
| CVE-2017-18342 | 50/100 | high-risk |
| CVE-2016-6924 | 50/100 | high-risk |
| CVE-2016-5363 | 50/100 | high-risk |
| CVE-2017-18318 | 50/100 | high-risk |