SARA / Free Tools / KEV Browser

CISA Known Exploited Vulnerabilities — searchable, filterable

Browse every CVE in the CISA KEV catalog. Filter by vendor, product, ransomware use, or BOD 22-01 due date. Updated daily from cisa.gov.

CVEVendorProductAddedDueRansom
CVE-2026-6973 Ivanti Endpoint Manager Mobile (EPMM) 2026-05-07 2026-05-10
CVE-2026-1281 Ivanti Endpoint Manager Mobile (EPMM) 2026-01-29 2026-02-01
CVE-2026-1603 Ivanti Endpoint Manager (EPM) 2026-03-09 2026-03-23
CVE-2026-1340 Ivanti Endpoint Manager Mobile (EPMM) 2026-04-08 2026-04-11
CVE-2025-4428 Ivanti Endpoint Manager Mobile (EPMM) 2025-05-19 2025-06-09
CVE-2025-4427 Ivanti Endpoint Manager Mobile (EPMM) 2025-05-19 2025-06-09
CVE-2025-22457 Ivanti Connect Secure, Policy Secure, and ZTA Gateways 2025-04-04 2025-04-11 Ransomware
CVE-2024-13161 Ivanti Endpoint Manager (EPM) 2025-03-10 2025-03-31
CVE-2024-13160 Ivanti Endpoint Manager (EPM) 2025-03-10 2025-03-31
CVE-2024-13159 Ivanti Endpoint Manager (EPM) 2025-03-10 2025-03-31
CVE-2025-0282 Ivanti Connect Secure, Policy Secure, and ZTA Gateways 2025-01-08 2025-01-15 Ransomware
CVE-2024-9380 Ivanti Cloud Services Appliance (CSA) 2024-10-09 2024-10-30
CVE-2024-9379 Ivanti Cloud Services Appliance (CSA) 2024-10-09 2024-10-30
CVE-2024-29824 Ivanti Endpoint Manager (EPM) 2024-10-02 2024-10-23
CVE-2024-7593 Ivanti Virtual Traffic Manager 2024-09-24 2024-10-15
CVE-2024-8963 Ivanti Cloud Services Appliance (CSA) 2024-09-19 2024-10-10
CVE-2024-8190 Ivanti Cloud Services Appliance 2024-09-13 2024-10-04
CVE-2021-44529 Ivanti Endpoint Manager Cloud Service Appliance (EPM CSA) 2024-03-25 2024-04-15 Ransomware
CVE-2024-21887 Ivanti Connect Secure and Policy Secure 2024-01-10 2024-01-22 Ransomware
CVE-2023-35082 Ivanti Endpoint Manager Mobile (EPMM) and MobileIron Core 2024-01-18 2024-02-08 Ransomware
CVE-2023-46805 Ivanti Connect Secure and Policy Secure 2024-01-10 2024-01-22 Ransomware
CVE-2024-21893 Ivanti Connect Secure, Policy Secure, and Neurons 2024-01-31 2024-02-02 Ransomware
CVE-2023-38035 Ivanti Sentry 2023-08-22 2023-09-12 Ransomware
CVE-2023-35081 Ivanti Endpoint Manager Mobile (EPMM) 2023-07-31 2023-08-21
CVE-2023-35078 Ivanti Endpoint Manager Mobile (EPMM) 2023-07-25 2023-08-15 Ransomware
CVE-2021-22893 Ivanti Pulse Connect Secure 2021-11-03 2022-05-03 Ransomware
CVE-2020-8243 Ivanti Pulse Connect Secure 2021-11-03 2022-05-03
CVE-2021-22900 Ivanti Pulse Connect Secure 2021-11-03 2022-05-03
CVE-2021-22894 Ivanti Pulse Connect Secure 2021-11-03 2022-05-03
CVE-2020-8260 Ivanti Pulse Connect Secure 2021-11-03 2022-05-03
CVE-2021-22899 Ivanti Pulse Connect Secure 2021-11-03 2022-05-03
CVE-2019-11510 Ivanti Pulse Connect Secure 2021-11-03 2022-05-03 Ransomware
CVE-2019-11539 Ivanti Pulse Connect Secure and Pulse Policy Secure 2021-11-03 2022-05-03 Ransomware
CVE-2020-15505 Ivanti MobileIron Multiple Products 2021-11-03 2022-05-03

ReferenceWhat is the CISA KEV catalog?

The Known Exploited Vulnerabilities (KEV) catalog is a CISA-maintained list of CVEs confirmed to be actively exploited in the wild. It is the authoritative answer to "is this vulnerability really being used by attackers?" Unlike EPSS (which is a probability), KEV is a binary, evidence-based signal — if a CVE is on the KEV list, it has been observed in real attacks.

For US federal agencies, BOD 22-01 makes remediation of KEV CVEs mandatory by the listed due date. For everyone else, KEV is the strongest possible "patch this now" signal you can get from public threat intel.

When to useWhen should I use KEV?

Patch prioritization

KEV is your strict "patch this immediately" tier. Anything in KEV outranks any EPSS or CVSS calculation in priority.

Compliance reporting

Federal agencies and federal contractors must show KEV remediation against BOD 22-01. KEV exposure is increasingly a question on cyber-insurance applications and audit checklists.

Tabletop exercises

Run "what if a KEV CVE matched our asset inventory tomorrow?" — most SOCs have never tested that pipeline end-to-end.

Threat-intel feeds

Pipe KEV diffs into your SIEM as a high-priority detection input. Anything new in KEV today should map to your environment within 24 hours.

ComparisonKEV vs EPSS vs CVSS — how do they fit together?

SignalWhat it answersUse
CVSSHow bad is this vulnerability if it is exploited?Severity (theoretical)
EPSSHow likely is this vulnerability to be exploited in the next 30 days?Probability (forecast)
KEVIs this vulnerability already being exploited, with public evidence?Binary (confirmed)

The right priority order, in plain English: anything in KEV is patched first. Among non-KEV items, sort by EPSS percentile descending. Use CVSS as a tiebreaker.

API

Want this in your SOAR or SIEM?

SARA Open ships an OpenAI-compatible API. Call POST /api/v1/analyze — SARA returns EPSS, CVSS, KEV status, and an analyst-grade written summary in one call.

curl -X POST https://sara-open.sirp.io/api/v1/analyze \
  -H "Authorization: Bearer $SARA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type": "cve", "value": "CVE-2021-44228"}'
Read the API reference →

FAQFrequently asked questions

How often does CISA update the KEV catalog?
Whenever new exploitation evidence is confirmed — typically several updates per month, sometimes multiple in a week. This browser refreshes from CISA daily and reflects the most recent ingest.
Is the KEV catalog mandatory for non-federal organizations?
No, but it is widely treated as the de-facto standard for must-patch prioritization, and is increasingly cited by cyber-insurers, auditors, and regulators.
What does ransomware use mean in the KEV catalog?
CISA flags CVEs known to have been exploited in ransomware campaigns. This is the highest-urgency tier for many SOCs and a frequent input to ransomware tabletop exercises.
Can I bulk-export the KEV catalog?
Yes. CISA publishes the full catalog as JSON and CSV directly. SARA's API additionally returns SARA's analyst-written summary alongside each row — useful for triage queues.
Does this browser show every KEV CVE, or just popular ones?
Every entry in the catalog. The full list is searchable here.
What is BOD 22-01?
Binding Operational Directive 22-01, issued by CISA, requires US federal civilian executive-branch agencies to remediate vulnerabilities in the KEV catalog by the listed due date. Most non-federal organizations adopt similar SLAs informally.

Browse related toolsKeep exploring

Looking for more?

Ask SARA — our AI security analyst — for full CVE context, exploit chains, and detection rules.

Try SARA