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
Our full local dataset: the complete known-exploited catalogue plus the high- and critical-severity CVEs published inside the collection window. It is a few thousand records, not the full CVE corpus; anything older and never exploited is not here.
| CVE | Title | Vendor | KEV listed | Published | EPSS | CVSS | Signals |
|---|---|---|---|---|---|---|---|
| CVE-2019-1297 | CVE-2019-1297 | Microsoft | 22% | 8.8, high | overdue patch 1 | ||
| CVE-2019-1253 | CVE-2019-1253 | Microsoft | 12% | 7.8, high | ransomware overdue exploit 1 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-1132 | CVE-2019-1132 | Microsoft | 10% | 7.8, high | overdue patch 1 | ||
| CVE-2019-1130 | CVE-2019-1130 | Microsoft | 2% | 7.8, high | ransomware overdue patch 1 | ||
| CVE-2019-1129 | CVE-2019-1129 | Microsoft | 2% | 7.8, high | ransomware overdue patch 1 | ||
| CVE-2019-1068 | CVE-2019-1068 | Microsoft | 57% | 8.8, high | overdue patch 1 | ||
| CVE-2019-0880 | CVE-2019-0880 | Microsoft | 2% | 7.8, high | overdue patch 1 | ||
| CVE-2019-1069 | CVE-2019-1069 | Microsoft | 6% | 7.8, high | ransomware overdue exploit 1 patch 2 | ||
| CVE-2019-1064 | CVE-2019-1064 | Microsoft | 7% | 7.8, high | ransomware overdue patch 2 | ||
| CVE-2019-0903 | CVE-2019-0903 | Microsoft | 22% | 8.8, high | overdue patch 1 | ||
| CVE-2019-0863 | CVE-2019-0863 | Microsoft | 5% | 7.8, high | overdue exploit 1 patch 1 | ||
| CVE-2019-0708 | CVE-2019-0708 | Microsoft | 100% | 9.8, critical | ransomware overdue exploit 5 patch 1 | ||
| CVE-2019-0859 | CVE-2019-0859 | Microsoft | 4% | 7.8, high | ransomware overdue patch 1 | ||
| CVE-2019-0841 | CVE-2019-0841 | Microsoft | 41% | 7.8, high | ransomware overdue exploit 6 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-0752 | CVE-2019-0752 | Microsoft | 82% | 7.5, high | ransomware overdue exploit 1 patch 1 | ||
| CVE-2019-0703 | CVE-2019-0703 | Microsoft | 10% | 6.5, medium | overdue patch 1 | ||
| CVE-2019-0676 | CVE-2019-0676 | Microsoft | 8% | 6.5, medium | overdue patch 1 advisory 1 | ||
| CVE-2019-0604 | CVE-2019-0604 | Microsoft | 100% | 9.8, critical | ransomware overdue patch 1 advisory 1 | ||
| CVE-2019-0543 | CVE-2019-0543 | Microsoft | 5% | 7.8, high | ransomware overdue exploit 1 patch 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-8639 | CVE-2018-8639 | Microsoft | 22% | 7.8, high | ransomware overdue patch 1 advisory 1 | ||
| CVE-2018-8611 | CVE-2018-8611 | Microsoft | 4% | 7.8, high | overdue patch 1 advisory 1 | ||
| CVE-2018-8589 | CVE-2018-8589 | Microsoft | 3% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2018-8581 | CVE-2018-8581 | Microsoft | 27% | 7.4, high | ransomware overdue patch 1 advisory 2 | ||
| CVE-2018-8453 | CVE-2018-8453 | Microsoft | 70% | 7.8, high | ransomware overdue exploit 2 patch 1 | ||
| CVE-2018-8440 | CVE-2018-8440 | Microsoft | 18% | 7.8, high | ransomware overdue exploit 1 patch 2 | ||
| CVE-2018-8414 | CVE-2018-8414 | Microsoft | 73% | 8.8, high | overdue patch 1 advisory 2 | ||
| CVE-2018-8406 | CVE-2018-8406 | Microsoft | 3% | 7.8, high | ransomware overdue patch 1 advisory 2 | ||
| CVE-2018-8405 | CVE-2018-8405 | Microsoft | 3% | 7.8, high | ransomware overdue patch 1 advisory 2 | ||
| CVE-2018-8373 | CVE-2018-8373 | Microsoft | 62% | 7.5, high | overdue patch 1 advisory 2 | ||
| CVE-2018-8174 | CVE-2018-8174 | Microsoft | 88% | 7.5, high | ransomware overdue exploit 2 patch 1 | ||
| CVE-2018-8120 | CVE-2018-8120 | Microsoft | 73% | 7, high | ransomware overdue exploit 1 patch 1 | ||
| CVE-2018-0824 | CVE-2018-0824 | Microsoft | 73% | 8.8, high | overdue exploit 1 patch 1 advisory 2 | ||
| 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-11882 | CVE-2017-11882 | Microsoft | 100% | 7.8, high | ransomware overdue exploit 10 patch 1 | ||
| CVE-2017-11826 | CVE-2017-11826 | Microsoft | 81% | 7.8, high | overdue exploit 2 patch 1 advisory 3 | ||
| CVE-2017-11774 | CVE-2017-11774 | Microsoft | 60% | 7.8, high | overdue exploit 1 patch 1 advisory 2 | ||
| CVE-2017-8759 | CVE-2017-8759 | Microsoft | 89% | 7.8, high | overdue exploit 3 patch 1 advisory 3 | ||
| CVE-2017-8570 | CVE-2017-8570 | Microsoft | 90% | 7.8, high | overdue exploit 2 patch 1 advisory 2 | ||
| CVE-2017-8543 | CVE-2017-8543 | Microsoft | 74% | 9.8, critical | overdue patch 1 advisory 2 | ||
| CVE-2017-8464 | CVE-2017-8464 | Microsoft | 90% | 8.8, high | overdue exploit 2 patch 1 advisory 2 | ||
| CVE-2017-8540 | CVE-2017-8540 | Microsoft | 72% | 7.8, high | overdue exploit 1 patch 1 advisory 2 | ||
| CVE-2017-0263 | CVE-2017-0263 | Microsoft | 10% | 7.8, high | overdue exploit 2 patch 1 advisory 2 | ||
| CVE-2017-0262 | CVE-2017-0262 | Microsoft | 81% | 7.8, high | overdue patch 1 advisory 1 | ||
| CVE-2017-0261 | CVE-2017-0261 | Microsoft | 78% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2017-0222 | CVE-2017-0222 | Microsoft | 30% | 8.8, high | overdue patch 1 advisory 2 | ||
| CVE-2017-0213 | CVE-2017-0213 | Microsoft | 84% | 7.3, high | ransomware overdue exploit 1 patch 1 | ||
| CVE-2017-0210 | CVE-2017-0210 | Microsoft | 22% | 8.8, high | overdue patch 1 advisory 2 | ||
| CVE-2017-0199 | CVE-2017-0199 | Microsoft | 99% | 7.8, high | ransomware overdue exploit 7 patch 1 | ||
| CVE-2017-7269 | CVE-2017-7269 | Microsoft | 100% | 9.8, critical | overdue exploit 5 patch 2 advisory 3 | ||
| CVE-2017-0149 | CVE-2017-0149 | Microsoft | 29% | 8.8, high | overdue patch 1 advisory 2 | ||
| CVE-2017-0148 | CVE-2017-0148 | Microsoft | 99% | 8.1, high | ransomware overdue exploit 4 patch 1 | ||
| CVE-2017-0147 | CVE-2017-0147 | Microsoft | 100% | 7.5, high | ransomware overdue exploit 5 patch 1 | ||
| CVE-2017-0146 | CVE-2017-0146 | Microsoft | 90% | 8.8, high | ransomware overdue exploit 5 patch 1 | ||
| CVE-2017-0145 | CVE-2017-0145 | Microsoft | 90% | 8.8, high | ransomware overdue exploit 4 patch 1 | ||
| CVE-2017-0144 | CVE-2017-0144 | Microsoft | 99% | 8.8, high | ransomware overdue exploit 6 patch 1 | ||
| CVE-2017-0143 | CVE-2017-0143 | Microsoft | 93% | 8.8, high | ransomware overdue exploit 5 patch 1 | ||
| CVE-2017-0101 | CVE-2017-0101 | Microsoft | 57% | 7.8, high | ransomware overdue exploit 1 patch 1 | ||
| CVE-2017-0059 | CVE-2017-0059 | Microsoft | 62% | 4.3, medium | overdue exploit 3 patch 1 advisory 2 | ||
| CVE-2017-0022 | CVE-2017-0022 | Microsoft | 18% | 6.5, medium | overdue exploit 1 patch 1 advisory 2 | ||
| CVE-2017-0005 | CVE-2017-0005 | Microsoft | 11% | 7.8, high | overdue exploit 1 patch 1 advisory 2 | ||
| CVE-2017-0001 | CVE-2017-0001 | Microsoft | 3% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2017-0037 | CVE-2017-0037 | Microsoft | 80% | 8.1, high | overdue exploit 5 patch 1 advisory 3 | ||
| CVE-2016-7262 | CVE-2016-7262 | Microsoft | 58% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2016-7256 | CVE-2016-7256 | Microsoft | 65% | 8.8, high | overdue patch 1 advisory 2 | ||
| CVE-2016-7255 | CVE-2016-7255 | Microsoft | 81% | 7.8, high | ransomware overdue exploit 5 patch 1 | ||
| CVE-2016-7201 | CVE-2016-7201 | Microsoft | 80% | 8.8, high | overdue exploit 4 patch 1 advisory 2 | ||
| CVE-2016-7200 | CVE-2016-7200 | Microsoft | 83% | 8.8, high | overdue exploit 4 patch 1 advisory 2 | ||
| CVE-2016-7193 | CVE-2016-7193 | Microsoft | 58% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2016-3393 | CVE-2016-3393 | Microsoft | 68% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2016-3298 | CVE-2016-3298 | Microsoft | 33% | 6.5, medium | overdue patch 2 advisory 2 | ||
| CVE-2016-3351 | CVE-2016-3351 | Microsoft | 26% | 6.5, medium | ransomware overdue exploit 1 patch 2 | ||
| CVE-2016-3309 | CVE-2016-3309 | Microsoft | 20% | 7.8, high | ransomware overdue exploit 1 patch 1 | ||
| CVE-2016-3235 | CVE-2016-3235 | Microsoft | 43% | 7.8, high | overdue exploit 3 patch 1 advisory 2 | ||
| CVE-2016-0189 | CVE-2016-0189 | Microsoft | 94% | 7.5, high | ransomware overdue exploit 2 patch 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-2016-0165 | CVE-2016-0165 | Microsoft | 14% | 7.8, high | overdue exploit 1 patch 1 advisory 2 | ||
| CVE-2016-0162 | CVE-2016-0162 | Microsoft | 22% | 4.3, medium | overdue patch 1 advisory 2 | ||
| CVE-2016-0151 | CVE-2016-0151 | Microsoft | 63% | 7.8, high | ransomware overdue exploit 1 patch 1 | ||
| CVE-2016-0099 | CVE-2016-0099 | Microsoft | 37% | 7.8, high | ransomware overdue exploit 4 patch 1 | ||
| CVE-2016-0040 | CVE-2016-0040 | Microsoft | 24% | 7.8, high | overdue exploit 1 patch 1 advisory 1 | ||
| CVE-2016-0034 | CVE-2016-0034 | Microsoft | 69% | 8.8, high | ransomware overdue patch 1 advisory 1 | ||
| CVE-2015-6175 | CVE-2015-6175 | Microsoft | 5% | 7.8, high | overdue patch 1 advisory 1 | ||
| CVE-2015-2546 | CVE-2015-2546 | Microsoft | 10% | 8.2, high | ransomware overdue patch 1 advisory 2 | ||
| CVE-2015-2545 | CVE-2015-2545 | Microsoft | 86% | 7.8, high | overdue exploit 1 patch 1 advisory 1 | ||
| CVE-2015-2502 | CVE-2015-2502 | Microsoft | 51% | 8.8, high | overdue exploit 1 patch 2 advisory 2 | ||
| CVE-2015-1769 | CVE-2015-1769 | Microsoft | 4% | 6.6, medium | overdue patch 1 advisory 2 | ||
| CVE-2015-1642 | CVE-2015-1642 | Microsoft | 53% | 7.8, high | overdue patch 1 advisory 2 | ||
| CVE-2015-2426 | CVE-2015-2426 | Microsoft | 87% | 8.8, high | overdue exploit 2 patch 1 advisory 3 | ||
| CVE-2015-2425 | CVE-2015-2425 | Microsoft | 45% | 8.8, high | overdue patch 1 advisory 1 | ||
| CVE-2015-2424 | CVE-2015-2424 | Microsoft | 40% | 8.8, high | overdue patch 1 advisory 1 | ||
| CVE-2015-2419 | CVE-2015-2419 | Microsoft | 53% | 8.8, high | overdue patch 1 advisory 1 | ||
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.