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-21643 Fortinet FortiClient EMS 2026-04-13 2026-04-16
CVE-2026-24858 Fortinet Multiple Products 2026-01-27 2026-01-30
CVE-2025-59718 Fortinet Multiple Products 2025-12-16 2025-12-23
CVE-2025-58034 Fortinet FortiWeb 2025-11-18 2025-11-25
CVE-2025-64446 Fortinet FortiWeb 2025-11-14 2025-11-21
CVE-2026-35616 Fortinet FortiClient EMS 2026-04-06 2026-04-09
CVE-2025-25257 Fortinet FortiWeb 2025-07-18 2025-08-08
CVE-2019-6693 Fortinet FortiOS 2025-06-25 2025-07-16 Ransomware
CVE-2025-32756 Fortinet Multiple Products 2025-05-14 2025-06-04
CVE-2025-24472 Fortinet FortiOS and FortiProxy 2025-03-18 2025-04-08 Ransomware
CVE-2024-55591 Fortinet FortiOS and FortiProxy 2025-01-14 2025-01-21 Ransomware
CVE-2024-47575 Fortinet FortiManager 2024-10-23 2024-11-13
CVE-2024-23113 Fortinet Multiple Products 2024-10-09 2024-10-30
CVE-2023-48788 Fortinet FortiClient EMS 2024-03-25 2024-04-15 Ransomware
CVE-2024-21762 Fortinet FortiOS 2024-02-09 2024-02-16 Ransomware
CVE-2023-27997 Fortinet FortiOS and FortiProxy SSL-VPN 2023-06-13 2023-07-04 Ransomware
CVE-2022-41328 Fortinet FortiOS 2023-03-14 2023-04-04
CVE-2022-42475 Fortinet FortiOS 2022-12-13 2023-01-03 Ransomware
CVE-2022-40684 Fortinet Multiple Products 2022-10-11 2022-11-01 Ransomware
CVE-2018-13374 Fortinet FortiOS and FortiADC 2022-09-08 2022-09-29 Ransomware
CVE-2018-13382 Fortinet FortiOS and FortiProxy 2022-01-10 2022-07-10 Ransomware
CVE-2018-13383 Fortinet FortiOS and FortiProxy 2022-01-10 2022-07-10 Ransomware
CVE-2021-44168 Fortinet FortiOS 2021-12-10 2021-12-24
CVE-2019-5591 Fortinet FortiOS 2021-11-03 2022-05-03
CVE-2020-12812 Fortinet FortiOS 2021-11-03 2022-05-03 Ransomware
CVE-2018-13379 Fortinet FortiOS 2021-11-03 2022-05-03 Ransomware

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