The last 30 days in numbers
| What we counted | Entries |
|---|---|
| Added to the catalog | 40 |
| CVSS 9.0 or more (critical) | 15 |
| No CVSS score in NVD yet | 0 |
| Due within 3 days of being added | 27 |
| Due 14 days after being added | 13 |
| CVE id 2 or more years older than the day added | 1 |
We asked our CVE tool for every entry added in the last 30 days, on 2026-11-05. Plex had the most entries from one vendor, with 4.
Three days to patch
Each KEV entry has two dates, the day CISA added it and the day the fix is due. For 27 of the 40 entries, the gap was 3 days or less. For 13, it was 14 days.
Whoever you work for, the due date is a fair clock. If CISA allows 3 days, a team that patches once a month is far behind.
Old bugs still get added
Exploited doesn't mean new. 1 of the entries carry a CVE id from 2 or more years before the day CISA added them, and the oldest is from 2,024.
On our first run, that group included a 2016 Apache Struts remote code execution bug, which the Struts team fixed back then. A server that missed that update is still open today.
Severity is not the same as being exploited
Only 15 of the 40 reach the critical band of CVSS. The rest are high, medium or low, yet each one has been used in real attacks.
That's why our guide to triaging CVEs with KEV, EPSS and CVSS puts a KEV listing ahead of the CVSS score. EPSS, the third signal, estimates the chance of exploitation in the next 30 days.
How to get the same list
The CVE Risk Check tool page lists the tools. Ask for the KEV entries of the last 1 to 90 days, filter by a product word such as "Cisco", and you get up to 50 back, newest first, with the CVSS score from NVD.
The same server has check_cve for one CVE in depth and triage_dependencies for deciding which of your dependencies to patch first. Our steps to add CVE Risk Check to Claude cover the setup.
Limits
A vendor here is the first word of CISA's entry name, so "Microsoft Windows" counts as Microsoft and a two-word vendor such as Palo Alto Networks shows up as "Palo". The window is 30 days back from the day of each refresh, so the numbers move as entries enter and leave it.
Try it: run the same check yourself with CVE Risk Check, with no key, or read every post on the Agent Tools blog.
Sources
- CISA, kev-data on GitHub: the KEV catalog as JSON and CSV, updated within minutes of cisa.gov, usually on weekdays.
- CISA, KEV JSON schema: each entry has the day it was added and the day its required action is due.
- FIRST, CVSS v4.0 specification: the severity scale: 7.0 to 8.9 is high, 9.0 to 10.0 is critical.
- FIRST, Exploit Prediction Scoring System: EPSS gives the chance that a CVE will be exploited in the next 30 days, updated daily.
- Apache Struts, Security Bulletin S2-032: the 2016 Struts remote code execution fix behind CVE-2016-3081.
- Our own runs: CVE Risk Check and the other tools named above, on 2026-11-05, 2026-11-11. A timer runs the same calls again every 7 to 30 days.
Change log
We measure the numbers in this post again every 7 to 30 days and check that every source still loads. A new line appears here only when something in the post really changed.
- 2026-11-11. Published. Why: First version, with the numbers we measured with our own tools on 2026-11-11.