# What is CISA KEV? The Known Exploited Vulnerabilities catalogue, explained

URL: https://sbombox.com/blog/what-is-cisa-kev
By SBOMBox SBOM experts. Published 2026-11-17

> CISA's KEV catalogue lists vulnerabilities attackers are exploiting now. What gets listed, the deadlines, how to check your SBOM and why it matters for the CRA.

Short answer: KEV is the Known Exploited Vulnerabilities catalogue, a free public list kept by the US Cybersecurity and Infrastructure Security Agency (CISA). Every entry is a CVE that attackers have been seen exploiting in the wild. If a component in your SBOM matches a KEV entry, treat it as your top priority: it is not a theoretical risk.

## Where the KEV catalogue comes from

CISA created the catalogue with Binding Operational Directive 22-01, issued on 3 November 2021. The directive requires US federal civilian agencies to fix listed vulnerabilities by a due date. Everyone else can use the same list for free, and most security teams now do, because it answers the one question CVSS cannot: is anybody actually using this?

> CISA maintains the authoritative source of vulnerabilities that have been exploited in the wild.
>
> — CISA, Known Exploited Vulnerabilities Catalog. [cisa.gov/known-exploited-vulnerabilities-catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)

## What it takes to get on the list

CISA adds a vulnerability only when all three criteria are met:

- It has a CVE ID.
- There is reliable evidence that it has been actively exploited.
- There is clear remediation guidance, such as a vendor patch or a mitigation.

The third rule matters. KEV is a list of things you can act on, not a list of every exploited flaw. A zero-day with no fix yet may be exploited but not listed until guidance exists.

## What a KEV entry contains

**Fields in each KEV entry**

| Field | What it tells you |
| --- | --- |
| cveID | The CVE identifier, for matching against your SBOM's vulnerability results |
| vendorProject, product | Who makes the affected product, in plain words |
| dateAdded | When CISA listed it: useful for 'what changed this week' reviews |
| requiredAction | What to do, usually 'apply mitigations per vendor instructions' |
| dueDate | The deadline for US federal agencies; a sensible benchmark for everyone |
| knownRansomwareCampaignUse | 'Known' if ransomware groups use it, otherwise 'Unknown' |
| cwes | The weakness type, such as CWE-502 deserialisation |

CISA publishes the catalogue as a web page, a CSV file and a JSON feed, so tools can poll it. It changes several times a week.

```bash
# Download the KEV feed and list the five most recent additions
curl -s https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json \
  | jq -r '.vulnerabilities | sort_by(.dateAdded) | reverse | .[0:5][] | "\(.dateAdded) \(.cveID) \(.product)"'
```

## How to check your SBOM against KEV

KEV lists CVEs, not packages, so you need two steps: find the CVEs that affect your components, then intersect them with the catalogue.

- 1. Generate an SBOM for the release you actually ship. See [how to generate one in GitHub Actions](https://sbombox.com/blog/sbom-github-actions) or [for a container image](https://sbombox.com/blog/container-image-sbom).
- 2. Match its components to known vulnerabilities. The [free SBOM vulnerability scanner](https://sbombox.com/tools/sbom-vulnerability-scanner) does this in your browser against OSV.
- 3. Flag every CVE that appears in KEV. Fix or mitigate those first, then record a [VEX statement](https://sbombox.com/blog/what-is-vex) for any that do not affect you.
- 4. Keep checking. A vulnerability you assessed last month can be added to KEV tomorrow. SBOMBox re-matches every stored SBOM daily and puts KEV hits at the top.

## KEV and the Cyber Resilience Act

Since 11 September 2026, manufacturers selling in the EU must report actively exploited vulnerabilities in their products: an early warning within 24 hours of becoming aware, then fuller notifications. The CRA defines an actively exploited vulnerability as one for which there is reliable evidence that a malicious actor has exploited it in a system without permission.

KEV is a US list and is not the CRA test. But a new KEV entry that matches a component in a product you sell is exactly the kind of evidence that should start your assessment, and your 24-hour clock may already be running once you confirm it. The EU's own [ENISA reporting process](https://sbombox.com/blog/enisa-cra-single-reporting-platform) and the [24-hour rule](https://sbombox.com/blog/cra-24-hour-reporting) explain what to send.

## KEV, EPSS and CVSS together

**Three signals, three questions**

| Signal | Question it answers | Source |
| --- | --- | --- |
| CISA KEV | Is this being exploited now? | CISA, yes/no list |
| EPSS | How likely is exploitation in the next 30 days? | FIRST, probability 0 to 1 |
| CVSS | How bad would exploitation be? | FIRST standard, score 0 to 10 |

Use KEV first, then [EPSS](https://sbombox.com/blog/what-is-epss), then CVSS. The full method is in [which vulnerabilities to fix first](https://sbombox.com/blog/which-vulnerabilities-to-fix-first).

## Frequently asked questions

### What does KEV stand for?

Known Exploited Vulnerabilities. CISA's KEV catalogue lists CVEs with reliable evidence of exploitation in the wild and clear remediation guidance.

### Is the CISA KEV catalogue mandatory?

Only for US federal civilian executive branch agencies, under Binding Operational Directive 22-01. For everyone else it is free, voluntary and widely used as the first filter for patching.

### How often is the KEV catalogue updated?

Several times a week, with no fixed schedule. Poll the JSON feed daily or use a tool that does it for you.

### Does a KEV entry mean I am affected?

No. It means the vulnerability is being exploited somewhere. You are affected only if your product contains the vulnerable component and the vulnerable code is reachable. Record the outcome as a VEX statement either way.

### Is a KEV-listed vulnerability 'actively exploited' under the CRA?

Not automatically: the CRA has its own definition. A KEV listing is strong evidence and should trigger your assessment straight away.

This is general information, not legal advice. Confirm how the rules apply to your products with counsel.
