Skip to content
CTEM Vendors

Home / Glossary / CISA Known Exploited Vulnerabilities (KEV) catalog

Glossary, read 12 Nov 2026

CISA Known Exploited Vulnerabilities (KEV) catalog, defined for a CTEM program

All termsStage Coverage Map

CISA Known Exploited Vulnerabilities (KEV) catalog in practice

BOD 22-01 (November 3, 2021) required federal agencies to fix listed flaws within two weeks, or six months for CVEs assigned before 2021. BOD 26-04 revoked BOD 22-01 and BOD 19-02 on June 10, 2026 and set timelines that start when CISA adds a flaw to KEV, shortening when exposure is public.

Outside government, KEV is the most common exploitation signal in prioritization. It is conservative by design: absence from KEV does not mean a flaw is unexploited, only that CISA has not confirmed it. Programs pair KEV with EPSS and local reachability. Many vendors ingest it directly; Brinqa, for example, documents a CISA due date risk factor.

An example

CISA's KEV feed for November 10, 2026 shows a Microsoft Office Outlook vulnerability among the newest additions, in catalog version 2026.11.10.

Source, read 12 Nov 2026.

Sources

  1. https://www.cisa.gov/known-exploited-vulnerabilities-catalog, read 12 Nov 2026
  2. https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities, read 12 Nov 2026
  3. https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk, read 12 Nov 2026
  4. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json, read 12 Nov 2026

Last reviewed 12 Nov 2026.