Kivorent News

Wednesday, November 18, 2026

Tech and AIExplainer

What CISA's Known Exploited Vulnerabilities catalog is, and why patch deadlines follow it

CISA's Known Exploited Vulnerabilities (KEV) catalog lists security flaws attackers are already using. Here is how a bug gets on it and what the deadlines mean.

Warden, covering security, outages and the rules for tech
, 3 min read

2 weeksusual deadline for agencies to fix a newly listed flaw

What to know

  • The KEV catalog is a public list, kept by the US Cybersecurity and Infrastructure Security Agency (CISA), of flaws with evidence of active exploitation.
  • A 2021 order, Binding Operational Directive 22-01, requires federal civilian agencies to fix listed flaws by a set due date.
  • Companies are not bound by it, but many use it to decide which patches to install first.

Security news often includes a line like "CISA added the flaw to its Known Exploited Vulnerabilities catalog." It appears in coverage of browser zero-days, monthly Patch Tuesday releases and attacks on IT management tools. The line is short, but it carries a specific meaning, and a deadline.

What the catalog is

The Known Exploited Vulnerabilities catalog, usually shortened to KEV, is a public list maintained by the US Cybersecurity and Infrastructure Security Agency (CISA). It holds security flaws that attackers are known to be using in real attacks, not just flaws that could in theory be abused.

That distinction is the point of the list. Software makers disclose thousands of vulnerabilities a year; a single Microsoft Patch Tuesday can fix more than a thousand. Only a small share of those are ever used by attackers. KEV is CISA's attempt to separate the flaws that are being exploited from the much longer list that merely exist.

CISA publishes the catalog on its website and as downloadable CSV and JSON files, so security teams can feed it into their own tools. Each entry names the product, the CVE number, a short description, the action to take, the date it was added and a due date. Entries also note whether the flaw is known to have been used in ransomware campaigns.

How a flaw gets listed

CISA uses three tests before adding an entry:

  • The flaw has a CVE ID, the standard identifier for publicly disclosed vulnerabilities. Our guide to reading a security advisory explains how those numbers work.
  • There is reliable evidence of active exploitation: attackers have used it, or tried to, against real systems. A proof-of-concept exploit sitting on a researcher's page is not enough on its own.
  • There is clear remediation guidance, such as a patch, an update or a vendor workaround, so the people told to act have something to do.

A flaw that is exploited before a fix exists is a zero-day. Many KEV entries start that way, and are added once the vendor ships a fix. Recent examples on this site include a Chrome zero-day and flaws in N-able's N-central remote management software.

Old bugs appear too. Attackers keep using flaws that were patched years ago on machines that never updated, so the catalog includes entries for software well past its prime.

What the due date means

CISA created the catalog in November 2021 alongside Binding Operational Directive 22-01. A binding operational directive is an order to federal civilian executive branch agencies, such as the departments of Commerce or Education. It does not cover the military, intelligence agencies, state governments or private companies.

Under the directive, those agencies must fix each listed flaw by its due date. When the directive launched, it set two weeks for vulnerabilities given CVE numbers in 2021 or later and six months for older ones, and CISA can set a shorter deadline when the risk calls for it. In practice, most new entries carry a due date about two to three weeks after they are added, which is why news stories often say agencies have "until" a certain date to patch.

How everyone else uses it

Companies, hospitals, schools and local governments are not required to follow KEV deadlines, but CISA urges them to, and many do. Vulnerability scanners and patch management tools commonly flag KEV entries, and some insurers and auditors ask about them.

The appeal is triage. A team that cannot patch everything at once can start with the flaws attackers are already using. The catalog does not replace a vendor's own severity rating, which measures how bad a flaw could be. It answers a different question: is anyone exploiting this right now?

Why it matters

When a flaw lands in the KEV catalog, the US government is saying it has evidence that attackers are using it, and it puts a date on the fix for federal agencies. For anyone running the affected software, that is the clearest public signal there is that a patch should move to the top of the list.

Internet, outages and security

Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.