← CRA Glossary
Security Standards & Frameworks

CISA Known Exploited Vulnerabilities (KEV) Catalogue

The CISA Known Exploited Vulnerabilities (KEV) catalogue is a curated list maintained by the US Cybersecurity and Infrastructure Security Agency that identifies CVEs for which there is credible evidence of active exploitation in the wild. For EU manufacturers, the KEV catalogue is the highest-priority vulnerability intelligence source - any KEV entry affecting a shipped product triggers the CRA's 24-hour ENISA notification obligation.

The CISA Known Exploited Vulnerabilities (KEV) catalogue is a curated list maintained by the US Cybersecurity and Infrastructure Security Agency that identifies CVEs for which there is credible evidence of active exploitation in the wild. For EU manufacturers, the KEV catalogue is the highest-priority vulnerability intelligence source - any KEV entry affecting a shipped product triggers the CRA's 24-hour ENISA notification obligation.

Security Standards & Frameworks

Last updated 19 July 2026

What Is the CISA KEV Catalogue?

The CISA Known Exploited Vulnerabilities (KEV) catalogue is a continuously updated list of CVEs that the US Cybersecurity and Infrastructure Security Agency (CISA) has determined are being actively exploited by threat actors in the wild. Unlike the NVD, which lists all known vulnerabilities, the KEV catalogue is a curated, high-signal subset: entry requires credible evidence of active exploitation - not theoretical exploitability. The catalogue is publicly accessible and machine-readable (JSON format), and is updated when CISA receives reliable exploitation evidence. As of 2025, the catalogue contains thousands of entries across a wide range of software and hardware products.

CRA reference:Article 14(1)

Why the KEV Catalogue Is Critical for CRA Compliance

Article 14(1) of the CRA requires manufacturers to notify ENISA within 24 hours of becoming aware that a vulnerability in their product is being actively exploited. The CISA KEV catalogue is the most reliable public signal of active exploitation. If a KEV entry is published for a CVE affecting a component in a manufacturer's shipped product, this is prima facie evidence that the Article 14(1) trigger has been met and the 24-hour notification clock has started. Manufacturers who monitor the KEV catalogue continuously and have it integrated with their SBOM management will know within hours whether a new KEV entry affects their products - enabling them to meet the notification deadline.

CRA reference:Article 14(1)

How Manufacturers Integrate KEV Monitoring

Manufacturers should integrate KEV monitoring into their vulnerability management workflow as a highest-priority alert source. Practical implementation includes: (1) subscribing to the CISA KEV RSS feed or API endpoint; (2) configuring SCA and SBOM management tools to cross-reference new KEV additions against the component inventory of all shipped products; (3) defining a specific incident response playbook for KEV matches - distinct from standard CVE triage - with a defined escalation path and ENISA notification template; (4) testing this playbook in regular tabletop exercises; and (5) ensuring the on-call product security team is alerted immediately when a KEV addition matches a shipped product component. Time-to-detect is critical given the 24-hour notification window.

CRA reference:Article 14(1), Article 13(3)

Common Mistakes

The most dangerous mistake is treating the KEV catalogue as a US-specific resource with no EU relevance. The CRA's active exploitation notification trigger is not geographically limited - exploitation evidence from any region, including KEV catalogue addition, counts as the trigger. Manufacturers who monitor only European threat intelligence sources will miss KEV additions that would trigger their Article 14(1) obligations. A second error is not having a KEV-specific response workflow: standard CVE triage processes are typically too slow (days to weeks) to meet the 24-hour notification window that KEV additions effectively trigger.

CRA reference:Article 14(1)

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Does a KEV catalogue addition automatically trigger the CRA's 24-hour ENISA notification?+

A KEV addition for a CVE affecting a component in a manufacturer's shipped product constitutes credible evidence that the vulnerability is actively exploited, which is the trigger for the Article 14(1) 24-hour notification obligation. Manufacturers should treat KEV additions affecting their products as triggering the notification clock from the moment they become aware of the KEV entry. They should not wait for independent confirmation of exploitation before beginning the notification process.

Is the CISA KEV catalogue relevant to EU manufacturers or only to US companies?+

The CISA KEV catalogue is a global vulnerability intelligence resource, not a US-only list. Active exploitation of software vulnerabilities is not geographically constrained - threat actors exploiting a vulnerability in the US are typically doing so globally. EU manufacturers and ENISA both use the KEV catalogue as a primary reference for actively exploited vulnerabilities. The CRA's notification obligation is triggered by active exploitation regardless of where in the world the exploitation is observed.

How frequently is the CISA KEV catalogue updated?+

The CISA KEV catalogue is updated on an ongoing basis as CISA receives and evaluates exploitation evidence. New entries can be added at any time, with multiple additions sometimes occurring in a single day during periods of high threat actor activity. Manufacturers should not rely on daily manual checks: the KEV API and JSON feed should be integrated into automated monitoring systems that alert the product security team immediately when a new entry is added that matches a component in their SBOM.

Sector checklists covering CISA Known Exploited Vulnerabilities (KEV) Catalogue

Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Smart Cameras & Video SurveillanceSmart cameras and IP video surveillance systems are frequently compromised via default credentials and unpatched firmware - they were among the first device classes targeted by Mirai and similar botnets. The CRA's prohibition on default passwords and requirement for secure update mechanisms directly target these failure modes. Manufacturers must also consider GDPR obligations around video data and the NIS2 implications for critical infrastructure deployments.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how CISA Known Exploited Vulnerabilities (KEV) Catalogue fits into your complete CRA compliance programme.

View checklists →