Skip to content
StratQuad

CISA Known Exploited Vulnerabilities (KEV) catalogue

4 min read

The US Cybersecurity and Infrastructure Security Agency's authoritative list of vulnerabilities with reliable evidence of exploitation in the wild.

At a glance

Owner
Cybersecurity and Infrastructure Security Agency (CISA)
Version
Continuously updated catalogue
Published
3 Nov 2021
Applies to
Mandatory for US federal civilian executive branch agencies; used worldwide as a prioritisation input
Mandatory
Mandatory for US federal civilian agencies under BOD 26-04; voluntary for everyone else
Assessed by
CISA decides inclusion
Cost model
Free, in CSV and JSON

Key points

  • A vulnerability enters KEV only when it has a CVE ID, reliable evidence of active exploitation, and clear remediation guidance.
  • Each entry has a CISA due date. Since June 2026, Binding Operational Directive (BOD) 26-04 sets risk based deadlines for US federal civilian agencies, weighing KEV listing, public exposure, whether exploitation can be automated, and how much control an attacker gains.
  • The shortest deadline, three days, applies to the highest risk KEV entries on publicly exposed assets; lower risk weaknesses get 14 or 60 days. BOD 22-01 created the catalogue in 2021 and set the earlier fixed defaults of two weeks for newer CVEs and six months for older ones.
  • The catalogue flags entries known to be used in ransomware campaigns.
  • Outside US government it carries no legal force, but it is widely used outside US government as a prioritisation input.

What it is

CISA launched the catalogue on 3 November 2021 alongside Binding Operational Directive (BOD) 22-01. Since June 2026, BOD 26-04 sets the deadlines. It answers one question: has this vulnerability been exploited in the real world? CISA adds entries as evidence emerges, often several a week, and the full list is published as CSV and JSON with a JSON schema.

Inclusion criteria

All three must be met:

  1. A CVE ID has been assigned.
  2. Active exploitation: there is reliable evidence that malicious code has been executed, or attempted, on a system without the owner's permission.
  3. Clear remediation guidance exists, such as a vendor update, or the affected product can be removed or retired.

CISA counts attempted exploitation, such as malicious code that runs on a honeypot or fails because the target system is not vulnerable. Scanning, security research and proof of concept code alone do not qualify, and a public proof of concept is not required for inclusion.

Catalogue fields

FieldContent
cveIDThe CVE identifier
vendorProject, productAffected vendor and product
vulnerabilityNameCISA's short name for the vulnerability
dateAddedDate the entry was added
shortDescriptionSummary of the flaw
requiredActionWhat to do, usually apply vendor updates or discontinue use
dueDateRemediation deadline for federal agencies
knownRansomwareCampaignUse"Known" or "Unknown"
notes, cwesReferences and weakness classifications

BOD 26-04 in brief

BOD 26-04, Prioritizing Security Updates Based on Risk (10 June 2026), applies to US federal civilian executive branch agencies. It replaces the fixed deadlines of BOD 22-01 with risk based ones: three days for the highest risk KEV entries on publicly exposed assets, and 14 or 60 days for lower risk weaknesses. In the highest risk cases agencies must also check whether the asset was compromised before the patch was applied. CISA encourages other organisations to take the same risk based approach and to prioritise KEV entries.

Using it well

Practitioner note

KEV is the cleanest prioritisation signal available because it is evidence based and short. Run your asset inventory and vulnerability scan results against the JSON feed daily, and treat any match on an internet facing asset as an incident level priority rather than a ticket in the normal patch cycle. Use the CISA due date as an outer limit, not a target: many KEV entries are exploited at scale within days of disclosure. Matches with knownRansomwareCampaignUse set to "Known" should be escalated further.

Evidence expected

To show a reviewer or board that KEV is managed, keep: the date each KEV entry was matched to your estate, the date it was remediated or mitigated, the time between the two against your own target, and any exceptions with a named risk owner.

Limitations

Limitations

  • KEV is a lagging indicator. An entry appears after exploitation is evidenced, so absence from KEV does not mean a vulnerability is safe.
  • It requires a CVE and a fix, so actively exploited flaws without either are excluded until they qualify.
  • It reflects CISA's visibility and US focus. Use UK sources such as NCSC advisories and NHS England cyber alerts alongside it.
  • It does not rank entries against each other. Combine with exposure, asset value and EPSS to order the work.

Sources

Suggest a correction