CVEs
Common Vulnerabilities and Exposures scored on severity, exploitability, and exposure.
243113 cves scored · Page 141 of 2432
critical-risk
762
high-risk
16121
moderate-risk
134619
low-risk
91611
| CVE | Score | Tier |
|---|---|---|
| CVE-2024-9935 | 51/100 | high-risk |
| CVE-2024-50340 | 51/100 | high-risk |
| CVE-2024-9916 | 51/100 | high-risk |
| CVE-2023-28766 | 51/100 | high-risk |
| CVE-2023-28241 | 51/100 | high-risk |
| CVE-2024-9054 | 51/100 | high-risk |
| CVE-2024-9676 | 51/100 | high-risk |
| CVE-2024-9061 | 51/100 | high-risk |
| CVE-2025-22607 | 51/100 | high-risk |
| CVE-2025-47330 | 51/100 | high-risk |
| CVE-2024-49357 | 51/100 | high-risk |
| CVE-2024-5008 | 51/100 | high-risk |
| CVE-2024-40766 | 51/100 | high-risk |
| CVE-2024-9193 | 51/100 | high-risk |
| CVE-2020-11250 | 51/100 | high-risk |
| CVE-2025-47166 | 51/100 | high-risk |
| CVE-2024-48456 | 51/100 | high-risk |
| CVE-2024-9634 | 51/100 | high-risk |
| CVE-2024-43046 | 51/100 | high-risk |
| CVE-2024-43056 | 51/100 | high-risk |
| CVE-2024-56325 | 51/100 | high-risk |
| CVE-2024-43067 | 51/100 | high-risk |
| CVE-2024-42416 | 51/100 | high-risk |
| CVE-2024-48208 | 51/100 | high-risk |
| CVE-2024-7188 | 51/100 | high-risk |
| CVE-2020-15050 | 51/100 | high-risk |
| CVE-2024-56340 | 51/100 | high-risk |
| CVE-2024-49035 | 51/100 | high-risk |
| CVE-2025-49551 | 51/100 | high-risk |
| CVE-2025-49550 | 51/100 | high-risk |
| CVE-2024-9643 | 51/100 | high-risk |
| CVE-2024-9459 | 51/100 | high-risk |
| CVE-2024-5441 | 51/100 | high-risk |
| CVE-2024-55879 | 51/100 | high-risk |
| CVE-2024-6781 | 51/100 | high-risk |
| CVE-2025-24200 | 51/100 | high-risk |
| CVE-2024-6842 | 51/100 | high-risk |
| CVE-2025-20116 | 51/100 | high-risk |
| CVE-2024-53009 | 51/100 | high-risk |
| CVE-2024-6893 | 51/100 | high-risk |
| CVE-2017-9629 | 51/100 | high-risk |
| CVE-2016-7006 | 51/100 | high-risk |
| CVE-2017-8275 | 51/100 | high-risk |
| CVE-2016-3134 | 51/100 | high-risk |
| CVE-2016-6953 | 51/100 | high-risk |
| CVE-2016-7131 | 51/100 | high-risk |
| CVE-2016-1481 | 51/100 | high-risk |
| CVE-2017-8331 | 51/100 | high-risk |
| CVE-2016-9315 | 51/100 | high-risk |
| CVE-2016-9253 | 51/100 | high-risk |
| CVE-2016-9249 | 51/100 | high-risk |
| CVE-2017-8408 | 51/100 | high-risk |
| CVE-2016-6952 | 51/100 | high-risk |
| CVE-2015-9130 | 51/100 | high-risk |
| CVE-2016-6947 | 51/100 | high-risk |
| CVE-2016-6948 | 51/100 | high-risk |
| CVE-2017-18764 | 51/100 | high-risk |
| CVE-2017-7375 | 51/100 | high-risk |
| CVE-2015-9123 | 51/100 | high-risk |
| CVE-2017-18001 | 51/100 | high-risk |
| CVE-2016-6951 | 51/100 | high-risk |
| CVE-2016-6628 | 51/100 | high-risk |
| CVE-2017-12965 | 51/100 | high-risk |
| CVE-2017-8471 | 51/100 | high-risk |
| CVE-2016-4105 | 51/100 | high-risk |
| CVE-2016-4104 | 51/100 | high-risk |
| CVE-2016-4103 | 51/100 | high-risk |
| CVE-2016-4101 | 51/100 | high-risk |
| CVE-2016-4100 | 51/100 | high-risk |
| CVE-2016-7140 | 51/100 | high-risk |
| CVE-2016-4099 | 51/100 | high-risk |
| CVE-2016-4098 | 51/100 | high-risk |
| CVE-2016-4787 | 51/100 | high-risk |
| CVE-2017-3508 | 51/100 | high-risk |
| CVE-2017-9454 | 51/100 | high-risk |
| CVE-2015-9115 | 51/100 | high-risk |
| CVE-2017-8473 | 51/100 | high-risk |
| CVE-2017-6145 | 51/100 | high-risk |
| CVE-2017-18072 | 51/100 | high-risk |
| CVE-2016-4097 | 51/100 | high-risk |
| CVE-2016-4096 | 51/100 | high-risk |
| CVE-2016-4094 | 51/100 | high-risk |
| CVE-2015-5471 | 51/100 | high-risk |
| CVE-2016-4093 | 51/100 | high-risk |
| CVE-2017-18648 | 51/100 | high-risk |
| CVE-2017-8481 | 51/100 | high-risk |
| CVE-2016-4090 | 51/100 | high-risk |
| CVE-2016-4089 | 51/100 | high-risk |
| CVE-2016-4088 | 51/100 | high-risk |
| CVE-2017-12987 | 51/100 | high-risk |
| CVE-2017-8485 | 51/100 | high-risk |
| CVE-2017-18638 | 51/100 | high-risk |
| CVE-2017-8490 | 51/100 | high-risk |
| CVE-2017-0882 | 51/100 | high-risk |
| CVE-2015-7346 | 51/100 | high-risk |
| CVE-2016-3690 | 51/100 | high-risk |
| CVE-2016-7185 | 51/100 | high-risk |
| CVE-2017-11512 | 51/100 | high-risk |
| CVE-2016-6950 | 51/100 | high-risk |
| CVE-2016-7134 | 51/100 | high-risk |