CVE Intelligence
Exploited and newly published vulnerabilities, ranked by whether they are being used, how likely they are to be, and whether a patch exists.
- CVEs held
- 3,164
- each with its own record page
- KEV listed, 30 days
- 35
- newest 16 Oct 2026
- Ransomware-linked
- 361
- confirmed by CISA
- Public exploit
- 883
- exploit code referenced
- Vendors
- 646
- named in affected products
- EPSS 90% or more
- 468
- 100% already known exploited
Counts of what we hold, not of every CVE ever filed. Collected from NVD, the CISA KEV catalogue (version 2026.10.16) and FIRST EPSS. Last collected .
Results
Every CVE in the CISA Known Exploited Vulnerabilities Catalog, with CVSS, EPSS and the references published for it. CISA lists a CVE only once there is evidence of exploitation against real targets, so this view answers what is being attacked, not what could be.
| CVE | Title | Vendor | KEV listed | Published | EPSS | CVSS | Signals |
|---|---|---|---|---|---|---|---|
| CVE-2021-34527 | CVE-2021-34527 | Microsoft | 100% | 8.8, high | ransomware overdue exploit 3 patch 2 | ||
| CVE-2021-34523 | CVE-2021-34523 | Microsoft | 100% | 9, critical | ransomware overdue exploit 1 patch 2 | ||
| CVE-2021-34473 | CVE-2021-34473 | Microsoft | 100% | 9.1, critical | ransomware overdue exploit 1 patch 2 | ||
| CVE-2021-34448 | CVE-2021-34448 | Microsoft | 40% | 6.8, medium | overdue patch 2 | ||
| CVE-2021-33771 | CVE-2021-33771 | Microsoft | 10% | 7.8, high | overdue patch 2 | ||
| CVE-2021-33742 | CVE-2021-33742 | Microsoft | 59% | 7.5, high | overdue patch 1 | ||
| CVE-2021-33739 | CVE-2021-33739 | Microsoft | 7% | 8.4, high | overdue patch 1 | ||
| CVE-2021-31979 | CVE-2021-31979 | Microsoft | 5% | 7.8, high | overdue patch 2 | ||
| CVE-2021-31956 | CVE-2021-31956 | Microsoft | 22% | 7.8, high | overdue patch 1 | ||
| CVE-2021-31955 | CVE-2021-31955 | Microsoft | 81% | 5.5, medium | overdue patch 1 | ||
| CVE-2021-31207 | CVE-2021-31207 | Microsoft | 100% | 6.6, medium | ransomware overdue exploit 1 patch 1 | ||
| CVE-2021-31201 | CVE-2021-31201 | Microsoft | 3% | 5.2, medium | overdue patch 1 | ||
| CVE-2021-31199 | CVE-2021-31199 | Microsoft | 3% | 5.2, medium | overdue patch 1 | ||
| CVE-2021-28550 | CVE-2021-28550 | Adobe | 52% | 8.8, high | overdue advisory 2 | ||
| CVE-2021-28310 | CVE-2021-28310 | Microsoft | 8% | 7.8, high | overdue patch 1 | ||
| CVE-2021-27085 | CVE-2021-27085 | Microsoft | 5% | 8.8, high | overdue patch 2 | ||
| CVE-2021-27065 | CVE-2021-27065 | Microsoft | 100% | 7.8, high | ransomware overdue exploit 2 patch 2 | ||
| CVE-2021-27059 | CVE-2021-27059 | Microsoft | 6% | 7.6, high | overdue patch 2 | ||
| CVE-2021-26858 | CVE-2021-26858 | Microsoft | 94% | 7.8, high | ransomware overdue patch 2 | ||
| CVE-2021-26857 | CVE-2021-26857 | Microsoft | 96% | 7.8, high | ransomware overdue patch 2 | ||
| CVE-2021-26855 | CVE-2021-26855 | Microsoft | 100% | 9.1, critical | ransomware overdue exploit 4 patch 2 | ||
| CVE-2021-26411 | CVE-2021-26411 | Microsoft | 81% | 8.8, high | ransomware overdue patch 2 | ||
| CVE-2021-21017 | CVE-2021-21017 | Adobe | 86% | 8.8, high | overdue advisory 2 | ||
| CVE-2021-1732 | CVE-2021-1732 | Microsoft | 78% | 7.8, high | ransomware overdue exploit 2 patch 1 | ||
| CVE-2021-1675 | CVE-2021-1675 | Microsoft | 85% | 7.8, high | ransomware overdue exploit 3 patch 1 | ||
| CVE-2021-1647 | CVE-2021-1647 | Microsoft | 39% | 7.8, high | overdue patch 2 | ||
| CVE-2020-4430 | CVE-2020-4430 | IBM | 69% | 4.3, medium | overdue exploit 2 patch 1 advisory 1 | ||
| CVE-2020-4428 | CVE-2020-4428 | IBM | 62% | 9.1, critical | overdue exploit 2 patch 1 advisory 1 | ||
| CVE-2020-4427 | CVE-2020-4427 | IBM | 70% | 9.8, critical | overdue exploit 2 patch 1 advisory 1 | ||
| CVE-2020-17144 | CVE-2020-17144 | Microsoft | 37% | 8.4, high | overdue patch 2 | ||
| CVE-2020-17087 | CVE-2020-17087 | Microsoft | 5% | 7.8, high | overdue patch 1 | ||
| CVE-2020-1472 | CVE-2020-1472 | Microsoft | 99% | 5.5, medium | ransomware overdue exploit 2 patch 2 | ||
| CVE-2020-1464 | CVE-2020-1464 | Microsoft | 39% | 7.8, high | overdue exploit 1 patch 1 advisory 2 | ||
| CVE-2020-1380 | CVE-2020-1380 | Microsoft | 24% | 7.8, high | overdue exploit 1 patch 1 | ||
| CVE-2020-1350 | CVE-2020-1350 | Microsoft | 97% | 10, critical | overdue exploit 1 patch 1 | ||
| CVE-2020-1147 | CVE-2020-1147 | Microsoft | 94% | 7.8, high | overdue exploit 4 patch 1 | ||
| CVE-2020-1054 | CVE-2020-1054 | Microsoft | 54% | 7, high | overdue exploit 1 patch 2 | ||
| CVE-2020-1040 | CVE-2020-1040 | Microsoft | 7% | 9, critical | overdue patch 1 advisory 1 | ||
| CVE-2020-1020 | CVE-2020-1020 | Microsoft | 65% | 8.8, high | overdue patch 1 | ||
| CVE-2020-0986 | CVE-2020-0986 | Microsoft | 16% | 7.8, high | overdue exploit 1 patch 1 | ||
| CVE-2020-0968 | CVE-2020-0968 | Microsoft | 31% | 7.5, high | ransomware overdue patch 1 | ||
| CVE-2020-0938 | CVE-2020-0938 | Microsoft | 69% | 7.8, high | overdue exploit 1 patch 1 | ||
| CVE-2020-0878 | CVE-2020-0878 | Microsoft | 3% | 4.2, medium | ransomware overdue patch 1 | ||
| CVE-2020-0688 | CVE-2020-0688 | Microsoft | 100% | 8.8, high | ransomware overdue exploit 2 patch 1 | ||
| CVE-2020-0683 | CVE-2020-0683 | Microsoft | 8% | 7.8, high | overdue patch 1 | ||
| CVE-2020-0674 | CVE-2020-0674 | Microsoft | 87% | 7.5, high | overdue exploit 4 patch 1 | ||
| CVE-2020-0646 | CVE-2020-0646 | Microsoft | 99% | 9.8, critical | overdue exploit 1 patch 1 | ||
| CVE-2020-0601 | CVE-2020-0601 | Microsoft | 89% | 8.1, high | overdue exploit 2 patch 1 | ||
| CVE-2019-4716 | CVE-2019-4716 | IBM | 86% | 9.8, critical | overdue exploit 2 patch 1 advisory 1 | ||
| CVE-2019-1429 | CVE-2019-1429 | Microsoft | 77% | 7.5, high | overdue exploit 1 patch 1 | ||
| CVE-2019-1367 | CVE-2019-1367 | Microsoft | 52% | 7.5, high | ransomware overdue patch 1 | ||
| CVE-2019-1215 | CVE-2019-1215 | Microsoft | 19% | 7.8, high | ransomware overdue patch 1 | ||
| CVE-2019-1214 | CVE-2019-1214 | Microsoft | 1% | 7.8, high | overdue patch 1 | ||
| CVE-2019-0863 | CVE-2019-0863 | Microsoft | 5% | 7.8, high | overdue exploit 1 patch 1 | ||
| CVE-2019-0859 | CVE-2019-0859 | Microsoft | 4% | 7.8, high | ransomware overdue patch 1 | ||
| CVE-2019-0808 | CVE-2019-0808 | Microsoft | 53% | 7.8, high | overdue exploit 1 patch 1 | ||
| CVE-2019-0803 | CVE-2019-0803 | Microsoft | 45% | 7.8, high | ransomware overdue exploit 1 patch 1 | ||
| CVE-2019-0797 | CVE-2019-0797 | Microsoft | 2% | 7.8, high | overdue patch 1 | ||
| CVE-2019-0708 | CVE-2019-0708 | Microsoft | 100% | 9.8, critical | ransomware overdue exploit 5 patch 1 | ||
| CVE-2019-0604 | CVE-2019-0604 | Microsoft | 100% | 9.8, critical | ransomware overdue patch 1 advisory 1 | ||
| CVE-2019-0541 | CVE-2019-0541 | Microsoft | 53% | 8.8, high | overdue exploit 1 patch 1 advisory 1 | ||
| CVE-2018-8653 | CVE-2018-8653 | Microsoft | 30% | 7.5, high | overdue patch 1 advisory 1 | ||
| CVE-2018-4939 | CVE-2018-4939 | Adobe | 62% | 9.8, critical | overdue advisory 3 | ||
| CVE-2018-4878 | CVE-2018-4878 | Adobe and 5 more vendors | 90% | 7.8, high | ransomware overdue exploit 2 advisory 13 | ||
| CVE-2018-15961 | CVE-2018-15961 | Adobe | 100% | 9.8, critical | overdue exploit 1 advisory 4 | ||
| CVE-2018-0802 | CVE-2018-0802 | Microsoft | 93% | 7.8, high | ransomware overdue exploit 3 patch 1 | ||
| CVE-2018-0798 | CVE-2018-0798 | Microsoft | 95% | 8.8, high | overdue patch 2 advisory 2 | ||
| CVE-2017-8759 | CVE-2017-8759 | Microsoft | 89% | 7.8, high | overdue exploit 3 patch 1 advisory 3 | ||
| CVE-2017-7269 | CVE-2017-7269 | Microsoft | 100% | 9.8, critical | overdue exploit 5 patch 2 advisory 3 | ||
| CVE-2017-11882 | CVE-2017-11882 | Microsoft | 100% | 7.8, high | ransomware overdue exploit 10 patch 1 | ||
| CVE-2017-11774 | CVE-2017-11774 | Microsoft | 60% | 7.8, high | overdue exploit 1 patch 1 advisory 2 | ||
| CVE-2017-0199 | CVE-2017-0199 | Microsoft | 99% | 7.8, high | ransomware overdue exploit 7 patch 1 | ||
| CVE-2017-0143 | CVE-2017-0143 | Microsoft | 93% | 8.8, high | ransomware overdue exploit 5 patch 1 | ||
| CVE-2016-7255 | CVE-2016-7255 | Microsoft | 81% | 7.8, high | ransomware overdue exploit 5 patch 1 | ||
| CVE-2016-3235 | CVE-2016-3235 | Microsoft | 43% | 7.8, high | overdue exploit 3 patch 1 advisory 2 | ||
| CVE-2016-0185 | CVE-2016-0185 | Microsoft | 70% | 7.8, high | overdue exploit 1 patch 1 advisory 3 | ||
| CVE-2016-0167 | CVE-2016-0167 | Microsoft | 6% | 7.8, high | ransomware overdue patch 1 advisory 2 | ||
| CVE-2015-1641 | CVE-2015-1641 | Microsoft | 97% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2014-1812 | CVE-2014-1812 | Microsoft | 65% | 8.8, high | ransomware overdue patch 1 advisory 1 | ||
| CVE-2012-0158 | CVE-2012-0158 | Microsoft | 100% | 8.8, high | ransomware overdue patch 1 advisory 10 | ||
How to read this
KEV means attacked, CVSS means attackable
CVSS scores how severe a flaw would be if exploited. The KEV date says CISA has evidence it is being exploited. A 7.5 in KEV is a more urgent patch than an unexploited 9.8.
EPSS is a probability, not a score
The modelled chance of exploitation activity in the next 30 days, from FIRST. The hairline under it is drawn to the same scale, so a short line really is a small chance.
Signals are a hint, not an inventory
exploit 3 means three references were classified as exploit code, from NVD's tags or the shape of the URL. overdue means a CISA remediation deadline has passed.
A slice, collected daily
The whole KEV catalogue, however old, plus the high and critical CVEs published in the last 90 days. Scores are as of the last collection, not the live upstream state. NVD holds the rest.