Explainer
CISA's Known Exploited Vulnerabilities (KEV) catalog explained
The Known Exploited Vulnerabilities (KEV) catalog is CISA's list of software flaws known to have been exploited in the wild, which it calls the authoritative source on the subject.[1] A flaw is added when it has a CVE ID, there is reliable evidence of active exploitation, and there is a clear fix.[2] US federal civilian agencies must fix listed flaws within set timeframes under Binding Operational Directive 26-04, issued in June 2026; other organizations are not bound but are urged to prioritize them.[3][4] The catalog listed 1,781 vulnerabilities as of November 13, 2026.[5]
What the catalog is
CISA, the US Cybersecurity and Infrastructure Security Agency, maintains the Known Exploited Vulnerabilities (KEV) catalog. It calls the catalog the authoritative source of vulnerabilities that have been exploited in the wild, and urges every organization to monitor it and prioritize fixing the flaws it lists.[1]
CISA set up the catalog in 2021 under Binding Operational Directive 22-01.[6] That directive described it as a CISA-managed list of known exploited vulnerabilities that carry significant risk to the federal enterprise.[7]
As of catalog version 2026.11.13, released on November 13, 2026, it listed 1,781 vulnerabilities.[5] Each entry includes a due date for federal agencies and a field showing whether the flaw is known to have been used in ransomware campaigns.[8]
How a vulnerability gets listed
CISA adds a vulnerability when three conditions are met: it has a CVE ID, there is reliable evidence that it has been actively exploited in the wild, and there is a clear remediation action, such as a vendor update.[2] CVE IDs come from the CVE Program, which CISA sponsors and which is run by a federally funded research and development center operated by MITRE.[9]
The test is whether a flaw has been exploited, not how easy it would be to exploit.[10] Attempted exploitation counts as well as successful exploitation. Scanning, security research of an exploit and proof-of-concept code do not.[11] CISA invites anyone with evidence that an unlisted flaw is being exploited to report it.[12]
For KEV vulnerabilities, CISA’s remediation action is to apply updates per vendor instructions. If the product is end-of-life or cannot be updated, it should be removed from the network.[13]
What federal agencies must do
Federal civilian executive branch agencies must remediate KEV vulnerabilities within timeframes set under BOD 26-04.[3] That directive, issued on June 10, 2026, carries forward the catalog criteria and supersedes and revokes BOD 22-01.[4]
Under BOD 22-01, the default deadline was six months for flaws with CVE IDs assigned before 2021 and two weeks for all others.[14] Under BOD 26-04, the urgency instead depends on four questions: whether the asset is publicly exposed, whether the flaw is in the KEV catalog, whether exploitation can be automated, and how much control an attacker gains.[15] The clock starts when CISA adds the flaw to the catalog or when the agency finds it on one of its systems, whichever comes first.[16]
Deadlines can be very short in urgent cases. CISA added the SharePoint “ToolShell” flaw CVE-2025-53770 on July 20, 2025, with a federal due date of July 21.[17] See the 2025 SharePoint ToolShell attacks.
How other organizations use it
The directive does not bind state and local governments or private companies, but CISA urges them to prioritize KEV vulnerabilities as well.[3] It says organizations should use the catalog as an input to their vulnerability management prioritization framework.[18] For related background, see zero-day vulnerabilities explained and the 2025 F5 source code breach.
Read next
The 2025 F5 source code breach and CISA Emergency Directive 26-01
What F5 disclosed about the 2025 breach of its BIG-IP development systems, why CISA issued Emergency Directive 26-01, and what agencies had to do.
Questions readers ask
What is the KEV catalog?
It is a list maintained by CISA of vulnerabilities that have been exploited in the wild. CISA calls it the authoritative source on such flaws and urges every organization to monitor it and prioritize fixing what is listed.[1]
How does a vulnerability get added?
It must have a CVE ID, there must be reliable evidence that it has been actively exploited in the wild, and there must be a clear remediation action, such as a vendor update.[2]
Does a public proof-of-concept exploit get a flaw listed?
No. CISA says scanning, security research of an exploit and proof-of-concept code do not count as active exploitation. Attempted and successful exploitation in the wild do count.[11]
Who has to follow it?
US federal civilian executive branch agencies must fix listed vulnerabilities within timeframes set under BOD 26-04. Other organizations, such as state and local governments and private companies, are not bound, but CISA urges them to prioritize the catalog too.[3]
How many vulnerabilities are listed?
The catalog listed 1,781 vulnerabilities in its November 13, 2026 version.[5]
Can I suggest a vulnerability for the catalog?
Yes. CISA invites organizations and individuals with evidence that an unlisted vulnerability is being actively exploited to report it.[12]
Sources
· 18 claims from 1 publisher
Each numbered claim is a statement we checked against the sources listed with it. Tap a number in the text to see its sources in place.
- [1]
CISA maintains the Known Exploited Vulnerabilities (KEV) catalog, which it calls the authoritative source of vulnerabilities exploited in the wild, and urges every organization to prioritize fixing the listed flaws. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source · Introduction (retrieved 2026-11-14)
- [2]
CISA adds a vulnerability to the KEV catalog when it has a CVE ID, there is reliable evidence of active exploitation, and there is a clear remediation action such as a vendor-provided update. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source · KEV catalog criteria (retrieved 2026-11-14)
- [3]
Federal civilian executive branch agencies must remediate vulnerabilities in the KEV catalog within timeframes set under BOD 26-04; other organizations are not bound by it but CISA urges them to prioritize KEV vulnerabilities too. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- [4]
Binding Operational Directive 26-04, issued on June 10, 2026, carries forward the KEV criteria and supersedes and revokes BOD 22-01 and BOD 19-02. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- BOD 26-04: Prioritizing Security Updates Based on Risk · CISA · Primary source · 2026-06-10 (retrieved 2026-11-14)
- BOD 26-04: Prioritizing Security Updates Based on Risk · CISA · Primary source · 2026-06-10 (retrieved 2026-11-14)
- [5]
CISA's KEV catalog listed 1,781 vulnerabilities in catalog version 2026.11.13, released on November 13, 2026. confirmedas of 2026-11-13
- CISA Catalog of Known Exploited Vulnerabilities (JSON feed, catalog version 2026.11.13) · CISA · Primary source · 2026-11-13 (retrieved 2026-11-14)
- CISA Catalog of Known Exploited Vulnerabilities (JSON feed, catalog version 2026.11.13) · CISA · Primary source · 2026-11-13 (retrieved 2026-11-14)
- [6]
CISA established the Known Exploited Vulnerabilities catalog in 2021 under Binding Operational Directive 22-01. confirmedas of 2026-11-14
- BOD 26-04: Prioritizing Security Updates Based on Risk · CISA · Primary source · 2026-06-10 (retrieved 2026-11-14)
- [7]
Binding Operational Directive 22-01 (November 2021) established a CISA-managed catalog of known exploited vulnerabilities that carry significant risk to the federal enterprise, which CISA describes as a risk-reduction action for federal civilian executive branch agencies. confirmedas of 2026-11-07
- BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source · 2021-11-03 (retrieved 2026-11-07)
- [8]
Each KEV catalog entry includes a due date for federal agencies and a field recording whether the vulnerability is known to have been used in ransomware campaigns. confirmedas of 2026-11-14
- CISA Catalog of Known Exploited Vulnerabilities (JSON feed, catalog version 2026.11.13) · CISA · Primary source · 2026-11-13 (retrieved 2026-11-14)
- CISA Catalog of Known Exploited Vulnerabilities (JSON feed, catalog version 2026.11.13) · CISA · Primary source · 2026-11-13 (retrieved 2026-11-14)
- [9]
The CVE Program, which assigns the identifiers the KEV catalog requires, is sponsored by CISA and run by a federally funded research and development center operated by MITRE. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- [10]
CISA says how easily a vulnerability could be exploited is not a criterion for the KEV catalog; the test is whether it has been exploited or is under active exploitation. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- [11]
For the KEV catalog, active exploitation includes attempted as well as successful exploitation, while scanning, security research of an exploit and proof-of-concept code do not count. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- [12]
CISA invites organizations and individuals to report evidence of actively exploited vulnerabilities not yet in the KEV catalog. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- [13]
CISA's remediation action for KEV vulnerabilities is to apply updates per vendor instructions, or remove the product from networks if it is end-of-life or cannot otherwise be updated. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
- [14]
Under BOD 22-01, agencies must remediate catalogued vulnerabilities within six months for CVE IDs assigned before 2021 and within two weeks for all others, unless CISA adjusts the timeline for grave risk. confirmedas of 2026-11-07
- BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source · 2021-11-03 (retrieved 2026-11-07)
- [15]
Under BOD 26-04, how quickly a federal agency must fix a vulnerability depends on whether the asset is publicly exposed, whether the flaw is in the KEV catalog, whether exploitation can be automated, and how much control an attacker gains. confirmedas of 2026-11-14
- BOD 26-04: Prioritizing Security Updates Based on Risk · CISA · Primary source · 2026-06-10 (retrieved 2026-11-14)
- BOD 26-04: Prioritizing Security Updates Based on Risk · CISA · Primary source · 2026-06-10 (retrieved 2026-11-14)
- [16]
Under BOD 26-04, an agency's remediation clock starts when CISA adds a vulnerability to the KEV catalog or when the agency identifies it on an asset, whichever comes first. confirmedas of 2026-11-14
- BOD 26-04: Prioritizing Security Updates Based on Risk · CISA · Primary source · 2026-06-10 (retrieved 2026-11-14)
- BOD 26-04: Prioritizing Security Updates Based on Risk · CISA · Primary source · 2026-06-10 (retrieved 2026-11-14)
- [17]
CISA added CVE-2025-53770 to its Known Exploited Vulnerabilities catalog on July 20, 2025, with a federal due date of July 21, and added CVE-2025-49704 and CVE-2025-49706 on July 22, 2025. confirmedas of 2026-11-14
- CISA Catalog of Known Exploited Vulnerabilities (JSON feed, catalog version 2026.11.13) · CISA · Primary source · 2026-11-13 · Entry CVE-2025-53770: "dateAdded": "2025-07-20", "dueDate": "2025-07-21" (retrieved 2026-11-14)
- CISA Catalog of Known Exploited Vulnerabilities (JSON feed, catalog version 2026.11.13) · CISA · Primary source · 2026-11-13 · Entry CVE-2025-53770 (retrieved 2026-11-14)
- CISA Catalog of Known Exploited Vulnerabilities (JSON feed, catalog version 2026.11.13) · CISA · Primary source · 2026-11-13 · Entries CVE-2025-49704 and CVE-2025-49706 (retrieved 2026-11-14)
- [18]
CISA says organizations should use the KEV catalog as an input to their vulnerability management prioritization framework. confirmedas of 2026-11-14
- Reducing the Significant Risk of Known Exploited Vulnerabilities · CISA · Primary source (retrieved 2026-11-14)
Revision history (1)
- Page created.
Created Nov 14, 2026. Last reviewed by an editor on Nov 15, 2026. Next scheduled review: Nov 14, 2027.
Cite this page
"CISA's Known Exploited Vulnerabilities (KEV) catalog explained." ContentLora, updated Nov 14, 2026. https://contentlora.com/explain/known-exploited-vulnerabilities-catalog
Spotted an error? Suggest a correction or emailcorrections@contentlora.com.