Security

The CISA KEV Catalog Explained: What Gets Listed and How a Small IT Team Uses It

A cinematic photograph of a misty beech forest at dusk, seen from low between the trunks, where three smooth gray trunks near the center carry a bright orange painted band at chest height while dozens of unmarked trees fade into the fog behind them, a visual for the KEV catalog: a short list of flaws confirmed as attacked and marked for action first

The KEV catalog is CISA’s public list of software flaws that attackers have used in the wild. KEV stands for Known Exploited Vulnerabilities. Each entry is one CVE with a required action, a date added and a due date. It is free, it is short compared with the full CVE list, and every entry is a flaw someone has used.

Our guide to what a CVE is gave KEV one section, next to CVSS and EPSS. This post goes deeper on the practical side. It covers what qualifies for a listing, what each field means, how to get the data, how often it changes and how to match it against the software your team runs.

The short version: if a flaw in software you run is in the KEV catalog, patch it first. Read the required action, then check the vendor advisory for affected versions, since the catalog does not list them. Get the data by email alert or by downloading the JSON or CSV file, and compare it with your software list on a schedule. A missing entry proves nothing. Plugin flaws are often attacked without ever being listed.

What gets a flaw into the KEV catalog

CISA’s KEV page sets three conditions. All three must be met.

  1. A CVE ID. The flaw has an assigned CVE. A bug fixed in a changelog with no ID cannot be listed.
  2. Active exploitation. There is reliable evidence that an attacker ran malicious code on a system without permission.
  3. Clear remediation. There is a clear action to take, such as a vendor update.

The second condition is the strict one. CISA counts attempted exploitation, including attacks that hit a honeypot, a decoy system built to catch attackers. It does not count scanning, security research or a public proof of concept. CISA also says a public exploit is not required for a listing.

The third condition explains some gaps. A flaw under attack with no fix yet waits until there is something to do. CISA’s page lists two main actions: apply the vendor’s update, or remove the product if it is end-of-life or cannot be updated. Mitigations and workarounds also count as interim steps.

What a listing tells you, and what it leaves out

A listing tells you one thing with confidence: attackers have used this flaw. It records what happened. Our post on EPSS covers the forecast side.

It leaves out three things a small team needs:

  • Affected versions. The catalog’s data schema has no version field. The notes field links to the vendor advisory. Read it.
  • Severity. There is no CVSS score in the entry. Our guide to reading a CVSS score covers that.
  • Whether you run it. Only your inventory answers that.

The catalog is also slow by design, because CISA needs evidence. The Bricksforge flaw from our Bricksforge post shows the gap. Patchstack reported automated attacks from October 7, 2026. The NVD record showed no KEV listing when we checked on October 21. For WordPress and Drupal add-ons, Wordfence, Patchstack, WPScan and Drupal’s advisories usually report attacks first.

Reading a KEV catalog entry, field by field

Each entry has the same fields in the CSV and JSON files. The names below are the JSON names.

Field What it holds How to use it
cveID The CVE ID The best key for matching against scanner output
vendorProject, product Vendor and product names, in CISA’s wording Map these to the names in your own inventory
vulnerabilityName, shortDescription A title and a short plain description Quick read on what an attacker gets
requiredAction What to do, usually apply vendor fixes or stop using the product Your to-do item
dateAdded The day CISA listed it Sort by this to see what is new
dueDate The federal deadline for the action A signal of urgency for everyone else
knownRansomwareCampaignUse “Known” or “Unknown” Known moves a flaw to the top
notes Links to the vendor advisory and NVD Where to find affected versions
cwes Weakness types, such as CWE-98 Useful for spotting patterns

Recent entries also carry a forensicTriage field, set to Yes or No. It does not appear in the published schema file, which CISA last updated in June 2024. Treat it as federal process detail unless CISA documents it further.

dateAdded and dueDate: what the KEV catalog deadlines mean

The two dates are the most used fields. dateAdded is when CISA confirmed the flaw belongs on the list. dueDate is when federal civilian agencies must finish the required action.

The gap between them varies by entry. In the data we read on October 21, 2026, the WordPress core flaw CVE-2026-87902 was added September 25 and due September 28. The LiteLLM flaw from our MCP authentication post was added September 2 and due September 16. Entries added October 14 to 16 each had a due date three days later.

One federal note. CISA lists BOD 22-01, the directive behind the original deadlines, as revoked, and recent entries cite BOD 26-04, which Tenable reports was issued on June 10, 2026.

The due date does not bind a nonprofit, a university or a private company. It is still a useful yardstick. A three-day window tells you how CISA rates the urgency.

knownRansomwareCampaignUse: Known versus Unknown

This field has two values. The catalog’s data schema defines "Known" as used in a ransomware campaign. "Unknown" means CISA does not have confirmation.

Treat Unknown as unconfirmed. Both the WordPress core and LiteLLM entries read Unknown when we checked.

Other sources can move first. In our GlobalProtect post, Palo Alto Networks’ Unit 42 named two ransomware groups exploiting CVE-2026-0257 on October 19, 2026. That flaw has been in the KEV catalog since May 29. If a vendor or a trusted researcher names ransomware, act on that, whatever the field says.

How to get KEV catalog data

There are four ways in. Pick the one that fits how your team works.

  • The web page. CISA’s catalog page is searchable and filterable. Good for a one-off lookup.
  • CSV and JSON files. The catalog page offers both, plus a JSON schema. The CSV opens in Excel or Google Sheets.
  • GitHub. CISA’s kev-data repository mirrors the same files. Its README says it updates shortly after cisa.gov and should be in sync within minutes. A developer can pull it in a script or watch the repository.
  • Email. The catalog page has a “Subscribe to the KEV Catalog Updates” option for alerts on new entries.

On RSS: in a May 2025 notice, CISA told RSS users who followed KEV updates to subscribe through its email service. A day later it paused that change. For a small team, the email alert is the simplest reliable option.

How often the KEV catalog updates

There is no fixed schedule. The GitHub README says CISA typically updates on weekdays during US Eastern business hours. In mid-October 2026, new entries landed on October 14, 15 and 16.

Each file carries a catalogVersion and a dateReleased value. Check those first. If the version has not changed since your last check, nothing new has been added.

A weekly comparison is enough for most small teams, with the email alert covering the days in between. An alert that names a product you run is a reason to check that day.

Matching the KEV catalog against your software list

The catalog is only useful once it meets your inventory. Here is a simple method.

  1. Keep a software list. Vendor, product and version for every server, firewall, VPN, CMS and major plugin. Include what your MSP manages.
  2. Match on CVE IDs first. If a scanner or plugin security service lists CVEs for your sites, compare those IDs with the catalog’s cveID column. An exact match is unambiguous.
  3. Then match on names. CISA’s names will not always match yours. WordPress core appears as vendor “WordPress”, product “Core”. LiteLLM appears under its maker, “BerriAI”. Keep a small mapping table.
  4. Confirm the version. For each hit, open the vendor advisory from the notes field and check your installed version against it.
  5. Record the result. Note the date, the catalog version and what you found, even when the answer is no match.

In a spreadsheet, an XLOOKUP on the CVE column does step two. A developer can do it with jq, a free command-line tool for JSON:

jq -r '.vulnerabilities[].cveID' known_exploited_vulnerabilities.json > kev-ids.txt
grep -Fx -f kev-ids.txt our-cves.txt

The first line pulls every CVE ID from the catalog. The second prints any line in your own CVE list that matches exactly.

What to do when you find a match

A match goes to the top of the queue. Here is the order we suggest, as our own rule of thumb:

  1. Apply the vendor fix, or the mitigation, today if the product faces the internet.
  2. If no fix applies, follow the required action. That can mean taking the product offline.
  3. Look for signs the flaw was used before you patched. Patching does not remove an attacker who got in first.
  4. If the ransomware field says Known, check backups and remote access too.

Our WordPress 7.1.3 post shows the version check in practice for core updates.

KEV catalog snapshot as of October 2026

These values change. They come from the CISA data files on GitHub and NVD records, read on October 21, 2026.

Item Value Note
Catalog version 2026.10.16 Released October 16, 2026
Entries 1,748 Total in that version
CVE-2026-87902 (WordPress core) Added September 25, due September 28 Ransomware use: Unknown
CVE-2026-59822 (LiteLLM) Added September 2, due September 16 Ransomware use: Unknown
CVE-2026-0257 (GlobalProtect) Added May 29, due June 1 Per the NVD record
CVE-2026-85097 (Bricksforge) Not listed Attacks reported by Patchstack from October 7

Check the live catalog before you rely on any row.

Frequently Asked Questions

What is the KEV catalog?

It is CISA’s list of software flaws with reliable evidence of exploitation in the wild. Each entry has a CVE ID, a required action, a date added and a due date.

What does a flaw need to be added to the KEV catalog?

Three things: a CVE ID, reliable evidence of active exploitation, and a clear remediation action such as a vendor update. A public proof of concept alone does not qualify.

Does the KEV catalog list affected versions?

No. The entry links to the vendor advisory in its notes field. Check your installed version against that advisory.

Do the due dates apply to nonprofits?

No. They are deadlines for federal civilian agencies. Other organizations can use them as a sign of how urgent CISA considers a flaw.

What does “Unknown” mean in the ransomware field?

It means CISA does not have confirmation of ransomware use. It does not mean the flaw has never been used by ransomware groups.

How often does CISA update the KEV catalog?

There is no fixed schedule. CISA typically updates on weekdays during US Eastern business hours. Check the catalogVersion value to see whether anything changed.

What is the easiest way to get alerts?

Use the email subscription on CISA’s catalog page. Developers can also pull the JSON file or watch CISA’s kev-data repository on GitHub.

Are WordPress plugin flaws in the KEV catalog?

Plugin flaws can be attacked without a listing. Bricksforge was under attack in October 2026 with no KEV listing when we checked. Follow Wordfence, Patchstack or WPScan for plugin attacks.

If a flaw is in KEV, does its EPSS or CVSS score matter?

Not for the first decision. A KEV listing means it has been exploited, so patch it first if you run an affected version. Scores help sort the flaws that are not listed.

Digital Matters

Security Desk