Leverage the CISA Known Exploited Vulnerabilities catalog alongside EPSS and CVSS to prioritize CVE remediation based on real-world exploitation evidence.
Leverage the CISA Known Exploited Vulnerabilities catalog alongside EPSS and CVSS to prioritize CVE remediation based on real-world exploitation evidence.
The CISA Known Exploited Vulnerabilities (KEV) catalog, established through Binding Operational Directive (BOD) 22-01, is a living list of CVEs that have been actively exploited in the wild and carry significant risk. As of early 2026, the catalog contains over 1,484 entries, growing 20% in 2025 alone with 245 new additions. This skill covers integrating the KEV catalog into vulnerability prioritization workflows alongside EPSS (Exploit Prediction Scoring System) and CVSS to create a risk-based approach that prioritizes vulnerabilities with confirmed exploitation activity over theoretical severity alone.
When to Use
When conducting security assessments that involve performing cve prioritization with kev catalog
When following incident response procedures for related security events
When performing scheduled security testing or auditing activities
When validating security controls through hands-on testing
Common Misconfigurations & Verification
Stale KEV/EPSS data — CISA updates multiple times weekly. Verify the catalog is refreshed daily before prioritizing.
CVSS-only triage — verify KEV and EPSS override pure severity (any KEV entry = P1 regardless of CVSS).
Ransomware flag ignored — verify knownRansomwareCampaignUse == "Known" entries get top urgency.
Non-KEV treated as safe — verify high-EPSS non-KEV CVEs still escalate; cataloging lags exploitation.
KEV due dates untracked — verify BOD 22-01 deadlines are tracked separately for FCEB compliance.
No environment match — verify a KEV CVE is actually present on your assets before paging, to cut noise.
Prerequisites
Access to vulnerability scan results (Qualys, Nessus, Rapid7, etc.)
Familiarity with CVE identifiers and NVD
Understanding of CVSS scoring (v3.1 and v4.0)
API access to CISA KEV, EPSS, and NVD endpoints
Python 3.8+ with requests and pandas libraries
Core Concepts
CISA KEV Catalog Structure
Each KEV entry contains:
CVE ID: The CVE identifier (e.g., CVE-2024-3094)
Vendor/Project: Affected vendor and product name
Vulnerability Name: Short description of the vulnerability
Date Added: When CISA added it to the catalog
Short Description: Brief technical description
Required Action: Recommended remediation action
Due Date: Deadline for federal agencies (FCEB) to remediate
Known Ransomware Campaign Use: Whether ransomware groups exploit it