CISA’s Known Exploited Vulnerabilities catalog: how entries are added, how BOD 26-04 uses it, and the feed, explained

CISA’s KEV catalog lists vulnerabilities with a CVE ID, reliable evidence of exploitation and a clear remediation. Federal civilian agencies must act on it under BOD 26-04; everyone else can use the public JSON and CSV feeds as a prioritization input.

The Known Exploited Vulnerabilities (KEV) catalog is CISA’s list of vulnerabilities that have been exploited in the wild. It began as a tool for federal agencies, and CISA recommends that every organization, including state and local governments and private industry, use it. This explainer covers what the catalog is, how a vulnerability gets in, how BOD 26-04 uses it, and how to consume the feed. Figures about the catalog’s size change as entries are added; read them from the feed, not from secondary summaries.

What the catalog is

CISA describes the KEV catalog as the authoritative source of vulnerabilities that have been exploited in the wild, and recommends that organizations use it as an input to their vulnerability management prioritization framework [1]. The catalog was established in 2021 under BOD 22-01, issued November 3, 2021 [6]. BOD 22-01 set two remediation windows: six months for CVE IDs assigned before 2021 and two weeks for all others [8]. That directive is now revoked and superseded by BOD 26-04 [8].

All federal civilian executive branch agencies must remediate KEV vulnerabilities within the timeframes set under BOD 26-04. CISA says that other organizations, including state, local, tribal and territorial governments and private industry, are not bound by the directive, and it strongly recommends they prioritize KEV remediation and include a requirement to address KEV vulnerabilities in their vulnerability management plans [2].

How a vulnerability is added

CISA’s criteria page sets three thresholds [2]:

  • An assigned CVE ID. The identifier comes through the CVE Program, which CISA sponsors and MITRE operates.
  • Reliable evidence of active exploitation in the wild. For the catalog, active exploitation includes attempted and successful exploitation, meaning malicious code executed by an actor without the system owner’s permission. How easily a flaw could be exploited is not a criterion, and a public proof of concept is neither required nor sufficient.
  • A clear remediation action, such as a vendor-provided update. Where a product is end-of-life or cannot be updated, the action is to remove it from agency networks.

The BOD 26-04 implementation guidance lists a fourth condition: that the vulnerability carries significant risk to U.S. government information systems [7]. The same guidance says CISA draws evidence from security vendors, researchers, government partners, open sources, commercial threat intelligence and its own incident response, adds only verifiable information, and aims to update the catalog within 24 hours of identifying an in-scope vulnerability, though research, evidence, missing mitigations or an unassigned CVE can delay additions [7].

Two answers in that guidance help in reading the catalog. Adding an older CVE does not necessarily mean CISA is observing exploitation now, since a vulnerability can qualify at any age. And CISA removes entries only rarely, for an error or a problem such as a harmful vendor update, and typically restores them once the issue is fixed [7].

How BOD 26-04 uses the catalog

BOD 26-04, Prioritizing Security Updates Based on Risk, was issued June 10, 2026. It revokes BOD 19-02 and BOD 22-01, and CISA says it carries the KEV criteria forward while folding the catalog into a wider set of patching decision points [2] [6]. Remediation urgency now depends on four variables: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether exploitation is automatable by an adversary, and whether exploitation gives partial or total control [6].

  • Clock start: the timeline begins when CISA adds a vulnerability to the catalog or when the agency identifies it on an asset and updates the CDM dashboard, whichever comes first. A new KEV listing shortens the timeline that applies [6].
  • Forensic triage: where the table calls for remediation “& forensic triage”, the agency must remediate or mitigate within three days and assess whether the system was compromised [6]. Each catalog entry now carries a forensicTriage field showing whether this applies [4].
  • Due dates: CISA calculates each entry’s dueDate from the BOD 26-04 timeline table using available data on exposure; for example, a publicly exposed, automatable vulnerability with total technical impact gets a three-day deadline. The agency makes the final exposure determination asset by asset [7].
  • CISA’s duties: keep the catalog and its criteria published, update it at the pace new KEVs are identified, and supply vulnerability metadata to the CVE database, as its Vulnrichment Program does [6].

The BOD 26-04 explainer covers the full timeline table and phases, and a data brief tracks the catalog’s 2026 additions.

The feed

The catalog page offers the data in machine-readable formats [1]. The JSON feed carries a header with the catalog title, a catalogVersion, a dateReleased timestamp and a count, followed by the list of vulnerabilities [3]. The published schema defines each entry’s fields [4]:

  • Identity: cveID, vendorProject, product and vulnerabilityName.
  • Description and action: shortDescription and requiredAction.
  • Dates: dateAdded and dueDate, both in YYYY-MM-DD format.
  • Context: knownRansomwareCampaignUse (“Known” or “Unknown”), forensicTriage (“Yes” or “No”), notes with references, and cwes.

The CSV file has the same columns [5]. The notes field on current entries links to the vendor advisory, BOD 26-04, the forensic triage guidance and the NVD record [3]. CISA’s description of the schema still calls the list a catalog of vulnerabilities “that carry significant risk to the federal enterprise”, a reminder that its scope is set by federal risk [4].

For organizations outside the federal government, in our view the practical pattern is to ingest the JSON feed on a schedule, match cveID against scanner and asset inventory output, and use dateAdded as the trigger for an internal clock. The dueDate is a federal deadline computed for federal assumptions; a company can adopt it, shorten it or set its own, and should record which it chose. CISA itself notes that the catalog is not the only list to track, because many vulnerabilities fall outside its scope [7]. These are practice points, not requirements on non-federal organizations.

This explainer is general information as checked on November 14, 2026, not legal advice.

Moraph’s teams help organizations with work like this. See our solutions.

Spotted an error? Tell us and we will check it and correct the explainer where needed.

  • CISA
  • Known Exploited Vulnerabilities
  • KEV
  • BOD 26-04
  • BOD 22-01
  • vulnerability management
  • patching