What is CISA's KEV catalog, and what does a KEV due date mean for you?

Cybersecurity

CISA’s Known Exploited Vulnerabilities (KEV) catalog is the U.S. cyber agency’s list of software flaws with reliable evidence of real-world exploitation, a CVE ID and a clear fix. Federal civilian agencies must patch listed flaws by a due date under BOD 26-04. CISA urges every organization to prioritize them too.

What is the CISA KEV catalog?

CISA, the Cybersecurity and Infrastructure Security Agency, calls the catalog “the authoritative source of vulnerabilities that have been exploited in the wild.” That wording is on CISA’s page explaining the KEV criteria, which we re-opened on November 14, 2026. You can search the live list on CISA’s Known Exploited Vulnerabilities catalog page.

The catalog was created in 2021 under Binding Operational Directive (BOD) 22-01. That directive has since been revoked. The current rules sit in BOD 26-04: Prioritizing Security Updates Based on Risk, issued June 10, 2026. BOD 26-04 says it “supersedes and hereby revokes” BOD 22-01.

The catalog had 1,781 entries as of November 14, 2026, according to CISA’s KEV JSON feed. When we re-pulled the feed at 8:49 PM CT that day, its count field was 1,781 and its catalogVersion was 2026.11.13, released at 2:24 PM CT on November 13 (dateReleased 2026-11-13T20:24:18.3008Z). The earliest dateAdded in the feed is 2021-11-03.

How a vulnerability gets on the list: CISA’s three criteria

CISA adds a flaw only when all three of these thresholds are met, as described on the criteria page.

It has a CVE ID

A CVE ID is a unique public identifier for a known software flaw. CISA links this to the CVE Program. Without a CVE ID, the flaw does not go in the catalog.

There is reliable evidence of active exploitation

CISA’s bar is evidence that someone ran malicious code against a real system without the owner’s permission. Attempted exploitation counts, including attacks that hit a honeypot. Scanning, security research and proof-of-concept code alone do not. CISA says a public proof-of-concept “does not automatically indicate the vulnerability has been or will be exploited.”

There is a clear remediation action

CISA adds a known exploited flaw when there is a clear action to take, such as a vendor update. If a product is at end-of-life or cannot be updated, the directive’s remediation path includes removing it from the network. Workarounds can be temporary; CISA still treats a vendor patch, when one exists, as the lasting fix.

Anyone can nominate an exploited flaw that is not already listed, through CISA’s KEV nomination and report form on the criteria page.

What is a KEV due date?

Each catalog entry has a dueDate. That date is the deadline for Federal Civilian Executive Branch (FCEB) agencies, not a claim that your home PC will be hacked on that day. KEV means “this flaw has been exploited somewhere,” not “you are already compromised.”

The 2026 rules (BOD 26-04)

BOD 26-04, issued June 10, 2026, is the current directive. It binds FCEB agencies. It does not apply to statutorily defined national security systems, or to certain systems operated by the Department of War or the Intelligence Community.

The clock is in calendar days. BOD 26-04 says the timelines in Table 1 begin when either (1) CISA adds the vulnerability to the KEV catalog, or (2) the agency identifies the vulnerability on an asset and updates its Continuous Diagnostics and Mitigation dashboard. “Whichever event occurs first starts the remediation timeline.”

For flaws that are already in the KEV catalog, Table 1 sets a 3-day or 14-day agency deadline, depending on whether the asset is publicly exposed, whether exploitation is automatable by an adversary, and whether the technical impact is partial or total control. This is a simplified readout of the KEV rows in Table 1: Remediation Timelines on the directive page (CISA, June 10, 2026; image re-opened November 14, 2026). The full 16-row table also covers flaws that are not in KEV.

If the asset is… Agency timeline for a KEV entry
Publicly exposed, and the flaw is automatable or gives total control (or both) 3 calendar days (plus forensic triage when the impact is total control)
Not publicly exposed, but the flaw is automatable and gives total control 3 calendar days and forensic triage
Any other KEV combination 14 calendar days

What “forensic triage” means

Where Table 1 says “3 days & forensic triage,” BOD 26-04 says the agency must finish the remediation or mitigation within three days “and carry out a forensic triage of the asset to assess whether the system is compromised.” An adequate triage, the directive says, follows CISA’s Forensic Triage Guidance in the implementation guide. The JSON feed also has a forensicTriage field, set to Yes or No, on each entry.

The old rule (BOD 22-01, 2021–2026)

This paragraph is history. BOD 22-01, issued November 3, 2021, used a simpler default: six months for vulnerabilities whose CVE ID was assigned before 2021, and two weeks for all others. CISA marked that directive revoked on June 10, 2026, and says it is superseded by BOD 26-04. Do not treat the old two-week and six-month clocks as current.

I’m not a federal agency. Does KEV apply to me?

Not as a legal mandate. BOD 26-04 binds FCEB agencies. “Unless directed by the governing procurement contract, this Directive does not apply to contractors,” the directive says, though it also tells FCEB agencies to review their contracts.

CISA still “strongly recommends all organizations review and monitor the KEV catalog and prioritize remediation of the listed vulnerabilities.” The FBI’s June 5, 2025 IC3 PSA on BADBOX 2.0 gives similar advice to the public: “Prioritize patching firewall vulnerabilities and known exploited vulnerabilities in internet-facing systems.”

Our advice, not CISA’s: if you run an internet-facing system, treat a KEV due date as your own outer deadline. For a first check on whether a given product even applies to you, start at our Am I affected? hub.

Worked example: php2shell

On October 26, 2026, CISA added two PHP flaws to the catalog, both with a due date of October 29, 2026, three days later. We pulled these fields from CISA’s KEV feed on November 14, 2026:

CISA added both php2shell CVEs to KEV on October 26. Our php2shell patch guide walks through the vendor fix.

Two other recent entries carry 14-day due dates. CISA added CVE-2026-111497, “Google Brotli Unchecked Return Value Vulnerability,” on October 27, 2026, with a due date of November 10, 2026 (our Node.js and Brotli check covers it). CISA added CVE-2026-19868, “SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability,” on November 6, 2026, with a due date of November 20, 2026 (see our SonicWall coverage).

The newest 3-day example landed on November 13, 2026: CVE-2026-123039, “Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability,” due November 16, 2026, with forensicTriage set to Yes. Our Check Point firewall check shows how to tell if yours was hit.

How to check the KEV catalog yourself

What KEV doesn’t tell you

The catalog is not a list of every exploited flaw. It is only the ones that meet all three criteria. A flaw can be dangerous and still be missing for a day or longer. The Brotli decoder flaw, CVE-2026-111497, is an example: it was not in the catalog on October 26, when we first covered it, and CISA added it on October 27.

The knownRansomwareCampaignUse field is either Known or Unknown. Unknown means CISA has not confirmed ransomware use, not that none exists. Our count from CISA’s feed on November 14, 2026, was 361 entries marked Known and 1,420 marked Unknown.

FAQ

What does KEV stand for?

Known Exploited Vulnerabilities.

What is a CISA KEV due date?

It is the remediation deadline for Federal Civilian Executive Branch agencies under BOD 26-04. The timeline is 3 or 14 calendar days from when CISA adds the flaw, or when the agency finds it, whichever comes first.

Do private companies have to follow KEV due dates?

No. The directive binds federal civilian agencies, not private companies, unless a contract says otherwise. CISA still urges every organization to prioritize KEV entries.

How does CISA decide what goes into KEV?

Three criteria: a CVE ID, reliable evidence of active exploitation, and a clear remediation action.

Is there a CISA KEV JSON feed or API?

CISA publishes a JSON feed and a CSV file, plus a JSON schema, at the links above. There is no separate public “API product” named on the pages we opened; the feed is a downloadable JSON file.

What replaced BOD 22-01?

BOD 26-04, issued June 10, 2026. It supersedes and revokes BOD 22-01.

Does KEV list every exploited vulnerability?

No. Only flaws that meet all three of CISA’s criteria.

What does “known ransomware campaign use” mean?

It is a CISA field on each entry, set to Known or Unknown. Unknown is not a finding that ransomware was never used.

Sources

  1. CISA, Known Exploited Vulnerabilities catalog. https://www.cisa.gov/known-exploited-vulnerabilities-catalog
  2. CISA, “Reducing the Significant Risk of Known Exploited Vulnerabilities” (criteria page). https://www.cisa.gov/known-exploited-vulnerabilities-catalog/reducing-significant-risk-known-exploited-vulnerabilities
  3. CISA, BOD 26-04, “Prioritizing Security Updates Based on Risk,” June 10, 2026. https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
  4. CISA, BOD 26-04 Table 1 image. https://www.cisa.gov/sites/default/files/2026-06/BOD_26-04_Table_1_Remediation_Timelines_0.png
  5. CISA, BOD 22-01, “Reducing the Significant Risk of Known Exploited Vulnerabilities” (revoked June 10, 2026). https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities
  6. CISA, KEV JSON feed. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
  7. CISA, KEV CSV. https://www.cisa.gov/sites/default/files/csv/known_exploited_vulnerabilities.csv
  8. CISA, KEV JSON schema. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities_schema.json
  9. FBI IC3, PSA I-060525-PSA, June 5, 2025. https://www.ic3.gov/PSA/2025/PSA250605
  10. CVE Program. https://www.cve.org/

All pages re-opened Saturday, November 14, 2026, between 8:49 and 8:51 PM CT. The KEV feed was re-pulled at 8:49 PM CT.