Skip to content
EPSS vs CVSS

SCORING SYSTEM, read 10 Nov 2026

The CISA KEV catalog is the one list of vulnerabilities with evidence of exploitation, and it lists after the fact, not before

CompareThe ledger

Maintained by
CISA (US Cybersecurity and Infrastructure Security Agency)
Scale
Binary: listed or not listed; fields include dateAdded, dueDate, knownRansomwareCampaignUse
Current version
Catalog version 2026.11.10, 1,779 entries (JSON feed read 2026-11-10)
Updated
On each addition; the feed carries catalogVersion and dateReleased
Answers
Whether there is reliable evidence that a CVE is being exploited in the wild

What it is and what the law says

BOD 22-01, issued 2021-11-03, was the original KEV directive and is now superseded. It established the catalog and stated that CISA would determine inclusion based on reliable evidence that the exploit is being actively used to exploit public or private organizations by a threat actor. It set default remediation times of two weeks, and six months for CVEs assigned before 2021.

On 2026-06-10 CISA issued BOD 26-04, Prioritizing Security Updates Based on Risk, the directive now in force. It states that it supersedes and revokes BOD 19-02 and BOD 22-01. The catalog continues: BOD 26-04 requires agencies to monitor KEV updates and remediate in accordance with the KEV remediation timelines. For federal readers this changes the citation, not the catalog.

The catalog URL and the JSON feed are separate things. The feed is the machine-readable file this site fetched; the web page presents the same entries with filters. For reproducible work, cite the feed and the catalogVersion.

The data in the feed

The JSON feed at cisa.gov carries a title, catalogVersion, dateReleased and a count, followed by the entries. On 2026-11-10 the catalogVersion was 2026.11.10 and the count was 1,779. Each entry has cveID, vendorProject, product, vulnerabilityName, dateAdded, shortDescription, requiredAction, dueDate, knownRansomwareCampaignUse, notes and cwes.

The feed has changed with BOD 26-04. Current entries also carry a forensicTriage field: on 2026-11-10, 103 of the 1,779 entries had the value Yes. In the 92 entries added from 2026-09-01 through 2026-11-10, 70 have a dueDate 3 days after dateAdded and 22 have one 14 days after, computed from the feed. The older two-week default is no longer the only deadline.

The ransomware field has two values in the data read: Known and Unknown. On 2026-11-10 the feed showed 361 entries marked Known out of 1,779, about 20 percent of the catalog. Among the 318 additions in the ledger window the share is 29, or 9.1 percent, lower than the whole catalog, and the field can be updated after an entry is listed.

How BOD 26-04 uses it

BOD 26-04 sets remediation urgency from four variables: asset exposure, KEV status, exploit automation and technical impact. CISA states that it publishes KEV status, exploit automation and technical impact for every CVE through the Vulnrichment program, and that agencies answer exposure themselves. The CERT/CC SSVC documentation describes the same four decision points as the CISA Response Timeline decision tree.

The outcomes are Fix on system upgrade, 60 days, 14 days, 3 days, and 3 days with forensic investigation. KEV is a decision point inside the tree, not the whole tree: a KEV entry on an internal asset with low impact can land on a different timeline than one on an internet-facing asset with total control.

Outcome (SSVC key)Definition
Fix on system upgrade (FSU)Remediate at the next scheduled major upgrade or rebuild
60 days (60D)Remediate within 60 days
14 days (14D)Remediate within 14 days
3 days (3D)Remediate within 3 days
3 days and forensic investigation (3DF)Remediate within 3 days and carry out a forensic triage of the asset

What the KEV Lag Ledger measures

The ledger takes every KEV entry with a dateAdded in the 365 days to the 2026-11-09 release: 318 additions. For each it takes the NVD published date and computes days from publication to listing in UTC calendar days.

The median is 10.5 days. 144 additions (45.3 percent) were listed within 7 days of NVD publication, 192 (60.4 percent) within 30 days, and 55 (17.3 percent) more than 365 days after publication. Eight were listed before the NVD published the record, giving negative values. The longest gap is 6,507 days. Additions per month ran from 9 in 2025-11 (a partial month) to 43 in 2026-09; 29 of the 318 carry knownRansomwareCampaignUse of Known.

Counting by month, additions ran 20 in 2025-12, 28 in 2026-02, 31 in 2026-04, 31 in 2026-08, 43 in 2026-09 and 36 in 2026-10. The 2026-11 figure is 7 because the window closes on 2026-11-09. A sizing exercise for remediation capacity should use the recent months, not the 318 divided by twelve.

What the lag means

A fast median hides a split. Almost half the additions are fresh vulnerabilities that attackers used within a week, and a sixth are old ones that surfaced again. For the fresh group, KEV adds confirmation after exploitation has begun. For the old group, a scanner that retired an old finding as low severity was holding something CISA later confirmed.

Keep two lists: new CVEs for which the question is whether they will reach KEV, and the existing backlog for which the question is whether KEV has since caught up. CISA publishes the catalog but not a prediction, so the first list needs EPSS or an equivalent.

Limits to state in the policy

KEV is a confirmed-exploitation list built from the evidence CISA has, and the original directive defined inclusion by significant risk to the federal enterprise. Absence from the catalog is not evidence of safety. The NVD, in its 2026-04-15 notice, gives KEV membership the top enrichment priority, with a goal of one business day, which makes KEV entries the best-documented records in the NVD.

The feed is a snapshot that moves daily. When a report cites a KEV count, cite the catalogVersion beside it.

For an auditor, the useful record is the list of KEV entries that applied to the organization, with the dateAdded, the dueDate the feed gave, and the date remediation completed. Those three dates produce the compliance figure directly.

Comparisons with this system

Sources

  1. CISA, KEV catalog JSON feed (catalogVersion 2026.11.10), read 10 Nov 2026
  2. CISA, BOD 26-04 (June 10, 2026), archived copy, read 10 Nov 2026
  3. CISA, BOD 22-01 (November 3, 2021, superseded), archived copy, read 10 Nov 2026
  4. CERT/CC SSVC, CISA BOD 26-04 Response Model, read 10 Nov 2026
  5. NVD news (2026-04-15 enrichment priorities), read 10 Nov 2026

Last reviewed 10 Nov 2026.