CVEs
Common Vulnerabilities and Exposures scored on severity, exploitability, and exposure.
243113 cves scored · Page 127 of 2432
critical-risk
762
high-risk
16121
moderate-risk
134619
low-risk
91611
| CVE | Score | Tier |
|---|---|---|
| CVE-2016-1022 | 52/100 | high-risk |
| CVE-2016-9452 | 52/100 | high-risk |
| CVE-2016-1024 | 52/100 | high-risk |
| CVE-2016-10452 | 52/100 | high-risk |
| CVE-2016-0273 | 52/100 | high-risk |
| CVE-2016-9451 | 52/100 | high-risk |
| CVE-2016-1029 | 52/100 | high-risk |
| CVE-2016-2388 | 52/100 | high-risk |
| CVE-2017-11496 | 52/100 | high-risk |
| CVE-2016-1032 | 52/100 | high-risk |
| CVE-2016-1033 | 52/100 | high-risk |
| CVE-2016-2799 | 52/100 | high-risk |
| CVE-2015-3616 | 52/100 | high-risk |
| CVE-2016-5730 | 52/100 | high-risk |
| CVE-2016-2097 | 52/100 | high-risk |
| CVE-2017-0252 | 52/100 | high-risk |
| CVE-2017-16598 | 52/100 | high-risk |
| CVE-2017-11497 | 52/100 | high-risk |
| CVE-2016-2800 | 52/100 | high-risk |
| CVE-2016-3168 | 52/100 | high-risk |
| CVE-2017-11235 | 52/100 | high-risk |
| CVE-2017-11256 | 52/100 | high-risk |
| CVE-2023-24906 | 52/100 | high-risk |
| CVE-2015-8240 | 52/100 | high-risk |
| CVE-2016-6376 | 52/100 | high-risk |
| CVE-2017-11724 | 52/100 | high-risk |
| CVE-2017-8116 | 52/100 | high-risk |
| CVE-2017-15118 | 52/100 | high-risk |
| CVE-2015-5338 | 52/100 | high-risk |
| CVE-2016-4194 | 52/100 | high-risk |
| CVE-2017-1000013 | 52/100 | high-risk |
| CVE-2016-5731 | 52/100 | high-risk |
| CVE-2015-8386 | 52/100 | high-risk |
| CVE-2017-17143 | 52/100 | high-risk |
| CVE-2017-15363 | 52/100 | high-risk |
| CVE-2016-1000112 | 52/100 | high-risk |
| CVE-2017-11769 | 52/100 | high-risk |
| CVE-2017-11224 | 52/100 | high-risk |
| CVE-2016-8363 | 52/100 | high-risk |
| CVE-2015-8617 | 52/100 | high-risk |
| CVE-2016-2801 | 52/100 | high-risk |
| CVE-2017-11223 | 52/100 | high-risk |
| CVE-2016-2790 | 52/100 | high-risk |
| CVE-2016-4576 | 52/100 | high-risk |
| CVE-2016-6657 | 52/100 | high-risk |
| CVE-2017-11505 | 52/100 | high-risk |
| CVE-2017-11530 | 52/100 | high-risk |
| CVE-2017-14698 | 52/100 | high-risk |
| CVE-2017-6019 | 52/100 | high-risk |
| CVE-2017-6017 | 52/100 | high-risk |
| CVE-2018-0301 | 52/100 | high-risk |
| CVE-2016-2791 | 52/100 | high-risk |
| CVE-2015-8863 | 52/100 | high-risk |
| CVE-2017-8587 | 52/100 | high-risk |
| CVE-2017-8495 | 52/100 | high-risk |
| CVE-2016-4107 | 52/100 | high-risk |
| CVE-2016-4102 | 52/100 | high-risk |
| CVE-2017-3768 | 52/100 | high-risk |
| CVE-2015-9136 | 52/100 | high-risk |
| CVE-2016-9856 | 52/100 | high-risk |
| CVE-2016-7233 | 52/100 | high-risk |
| CVE-2015-8980 | 52/100 | high-risk |
| CVE-2017-17144 | 52/100 | high-risk |
| CVE-2016-0763 | 52/100 | high-risk |
| CVE-2017-17151 | 52/100 | high-risk |
| CVE-2016-4462 | 52/100 | high-risk |
| CVE-2017-14086 | 52/100 | high-risk |
| CVE-2016-4607 | 52/100 | high-risk |
| CVE-2016-3542 | 52/100 | high-risk |
| CVE-2016-0173 | 52/100 | high-risk |
| CVE-2017-12567 | 52/100 | high-risk |
| CVE-2016-0171 | 52/100 | high-risk |
| CVE-2016-2802 | 52/100 | high-risk |
| CVE-2017-8333 | 52/100 | high-risk |
| CVE-2017-7752 | 52/100 | high-risk |
| CVE-2016-1659 | 52/100 | high-risk |
| CVE-2016-0898 | 52/100 | high-risk |
| CVE-2017-7105 | 52/100 | high-risk |
| CVE-2015-7687 | 52/100 | high-risk |
| CVE-2017-11219 | 52/100 | high-risk |
| CVE-2017-13179 | 52/100 | high-risk |
| CVE-2015-9262 | 52/100 | high-risk |
| CVE-2017-10981 | 52/100 | high-risk |
| CVE-2015-6319 | 52/100 | high-risk |
| CVE-2015-8556 | 52/100 | high-risk |
| CVE-2017-3737 | 52/100 | high-risk |
| CVE-2016-4185 | 52/100 | high-risk |
| CVE-2017-11218 | 52/100 | high-risk |
| CVE-2017-16845 | 52/100 | high-risk |
| CVE-2017-8404 | 52/100 | high-risk |
| CVE-2016-2804 | 52/100 | high-risk |
| CVE-2016-3279 | 52/100 | high-risk |
| CVE-2017-7005 | 52/100 | high-risk |
| CVE-2017-5824 | 52/100 | high-risk |
| CVE-2017-7273 | 52/100 | high-risk |
| CVE-2017-7108 | 52/100 | high-risk |
| CVE-2017-1000054 | 52/100 | high-risk |
| CVE-2016-1301 | 52/100 | high-risk |
| CVE-2017-16418 | 52/100 | high-risk |
| CVE-2017-4917 | 52/100 | high-risk |