CVEs
Common Vulnerabilities and Exposures scored on severity, exploitability, and exposure.
243113 cves scored · Page 32 of 2432
critical-risk
762
high-risk
16121
moderate-risk
134619
low-risk
91611
| CVE | Score | Tier |
|---|---|---|
| CVE-2021-37926 | 61/100 | high-risk |
| CVE-2020-36184 | 61/100 | high-risk |
| CVE-2021-37928 | 61/100 | high-risk |
| CVE-2021-26432 | 61/100 | high-risk |
| CVE-2021-3493 | 61/100 | high-risk |
| CVE-2021-24093 | 61/100 | high-risk |
| CVE-2021-43222 | 61/100 | high-risk |
| CVE-2020-0994 | 61/100 | high-risk |
| CVE-2020-1401 | 61/100 | high-risk |
| CVE-2021-1906 | 61/100 | high-risk |
| CVE-2021-28329 | 61/100 | high-risk |
| CVE-2021-31979 | 61/100 | high-risk |
| CVE-2021-28354 | 61/100 | high-risk |
| CVE-2021-33749 | 61/100 | high-risk |
| CVE-2021-25298 | 61/100 | high-risk |
| CVE-2020-1448 | 61/100 | high-risk |
| CVE-2021-28337 | 61/100 | high-risk |
| CVE-2021-46773 | 61/100 | high-risk |
| CVE-2021-37761 | 61/100 | high-risk |
| CVE-2021-37762 | 61/100 | high-risk |
| CVE-2021-28338 | 61/100 | high-risk |
| CVE-2021-26690 | 61/100 | high-risk |
| CVE-2021-28339 | 61/100 | high-risk |
| CVE-2021-3449 | 61/100 | high-risk |
| CVE-2021-38646 | 61/100 | high-risk |
| CVE-2021-34568 | 61/100 | high-risk |
| CVE-2021-28353 | 61/100 | high-risk |
| CVE-2020-1495 | 61/100 | high-risk |
| CVE-2025-64421 | 61/100 | high-risk |
| CVE-2025-54264 | 61/100 | high-risk |
| CVE-2025-64425 | 61/100 | high-risk |
| CVE-2025-4576 | 61/100 | high-risk |
| CVE-2025-59158 | 61/100 | high-risk |
| CVE-2017-11882 | 61/100 | high-risk |
| CVE-2016-4264 | 61/100 | high-risk |
| CVE-2017-16943 | 61/100 | high-risk |
| CVE-2016-9865 | 61/100 | high-risk |
| CVE-2017-0303 | 61/100 | high-risk |
| CVE-2016-9877 | 61/100 | high-risk |
| CVE-2017-16995 | 61/100 | high-risk |
| CVE-2017-12229 | 61/100 | high-risk |
| CVE-2016-4340 | 61/100 | high-risk |
| CVE-2017-12337 | 61/100 | high-risk |
| CVE-2016-0742 | 61/100 | high-risk |
| CVE-2017-3136 | 61/100 | high-risk |
| CVE-2016-0937 | 61/100 | high-risk |
| CVE-2017-5944 | 61/100 | high-risk |
| CVE-2016-0800 | 61/100 | high-risk |
| CVE-2016-0933 | 61/100 | high-risk |
| CVE-2015-7747 | 61/100 | high-risk |
| CVE-2016-6380 | 61/100 | high-risk |
| CVE-2016-7405 | 61/100 | high-risk |
| CVE-2016-7399 | 61/100 | high-risk |
| CVE-2017-15889 | 61/100 | high-risk |
| CVE-2018-0125 | 61/100 | high-risk |
| CVE-2015-8352 | 61/100 | high-risk |
| CVE-2017-14251 | 61/100 | high-risk |
| CVE-2016-2088 | 61/100 | high-risk |
| CVE-2015-8391 | 61/100 | high-risk |
| CVE-2016-1525 | 61/100 | high-risk |
| CVE-2017-9765 | 61/100 | high-risk |
| CVE-2017-5507 | 61/100 | high-risk |
| CVE-2017-6971 | 61/100 | high-risk |
| CVE-2017-6972 | 61/100 | high-risk |
| CVE-2016-2161 | 61/100 | high-risk |
| CVE-2016-6079 | 61/100 | high-risk |
| CVE-2017-4992 | 61/100 | high-risk |
| CVE-2016-0638 | 61/100 | high-risk |
| CVE-2016-0635 | 61/100 | high-risk |
| CVE-2017-7047 | 61/100 | high-risk |
| CVE-2017-0059 | 61/100 | high-risk |
| CVE-2017-0063 | 61/100 | high-risk |
| CVE-2017-0083 | 61/100 | high-risk |
| CVE-2015-1769 | 61/100 | high-risk |
| CVE-2017-0086 | 61/100 | high-risk |
| CVE-2016-2208 | 61/100 | high-risk |
| CVE-2017-0087 | 61/100 | high-risk |
| CVE-2017-0088 | 61/100 | high-risk |
| CVE-2017-13696 | 61/100 | high-risk |
| CVE-2017-1000375 | 61/100 | high-risk |
| CVE-2017-0090 | 61/100 | high-risk |
| CVE-2017-9080 | 61/100 | high-risk |
| CVE-2016-2296 | 61/100 | high-risk |
| CVE-2016-5423 | 61/100 | high-risk |
| CVE-2016-2298 | 61/100 | high-risk |
| CVE-2016-8749 | 61/100 | high-risk |
| CVE-2017-1000254 | 61/100 | high-risk |
| CVE-2017-6168 | 61/100 | high-risk |
| CVE-2016-3987 | 61/100 | high-risk |
| CVE-2016-2386 | 61/100 | high-risk |
| CVE-2016-9086 | 61/100 | high-risk |
| CVE-2016-1264 | 61/100 | high-risk |
| CVE-2017-0210 | 61/100 | high-risk |
| CVE-2016-3510 | 61/100 | high-risk |
| CVE-2017-3549 | 61/100 | high-risk |
| CVE-2017-7411 | 61/100 | high-risk |
| CVE-2015-3405 | 61/100 | high-risk |
| CVE-2017-7890 | 61/100 | high-risk |
| CVE-2016-3368 | 61/100 | high-risk |
| CVE-2016-7836 | 61/100 | high-risk |