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-2441 Google Chromium 2026-02-17 2026-03-10
CVE-2025-14174 Google Chromium 2025-12-12 2026-01-02
CVE-2025-13223 Google Chromium V8 2025-11-19 2025-12-10
CVE-2025-10585 Google Chromium V8 2025-09-23 2025-10-14
CVE-2026-3910 Google Chromium V8 2026-03-13 2026-03-27
CVE-2026-3909 Google Skia 2026-03-13 2026-03-27
CVE-2026-5281 Google Dawn 2026-04-01 2026-04-15
CVE-2025-6558 Google Chromium 2025-07-22 2025-08-12
CVE-2025-6554 Google Chromium V8 2025-07-02 2025-07-23
CVE-2025-5419 Google Chromium V8 2025-06-05 2025-06-26
CVE-2025-2783 Google Chromium Mojo 2025-03-27 2025-04-17
CVE-2024-7965 Google Chromium V8 2024-08-28 2024-09-18
CVE-2024-7971 Google Chromium V8 2024-08-26 2024-09-16
CVE-2024-4761 Google Chromium V8 2024-05-16 2024-06-06
CVE-2024-4671 Google Chromium 2024-05-13 2024-06-03
CVE-2024-5274 Google Chromium V8 2024-05-28 2024-06-18
CVE-2024-4947 Google Chromium V8 2024-05-20 2024-06-10
CVE-2024-0519 Google Chromium V8 2024-01-17 2024-02-07
CVE-2023-4762 Google Chromium V8 2024-02-06 2024-02-27
CVE-2023-5217 Google Chromium libvpx 2023-10-02 2023-10-23
CVE-2023-4863 Google Chromium WebP 2023-09-13 2023-10-04
CVE-2023-6345 Google Chromium Skia 2023-11-30 2023-12-21
CVE-2023-7024 Google Chromium WebRTC 2024-01-02 2024-01-23
CVE-2023-3079 Google Chromium V8 2023-06-07 2023-06-28
CVE-2023-2136 Google Chromium Skia 2023-04-21 2023-05-12
CVE-2023-2033 Google Chromium V8 2023-04-17 2023-05-08
CVE-2022-3038 Google Chromium Network Service 2023-03-30 2023-04-20
CVE-2022-4262 Google Chromium V8 2022-12-05 2022-12-26
CVE-2022-3723 Google Chromium V8 2022-10-28 2022-11-18
CVE-2022-4135 Google Chromium GPU 2022-11-28 2022-12-19
CVE-2022-2856 Google Chromium Intents 2022-08-18 2022-09-08
CVE-2022-3075 Google Chromium Mojo 2022-09-08 2022-09-29
CVE-2021-30533 Google Chromium PopupBlocker 2022-06-27 2022-07-18
CVE-2019-5825 Google Chromium V8 2022-06-08 2022-06-22
CVE-2016-5198 Google Chromium V8 2022-06-08 2022-06-22
CVE-2016-1646 Google Chromium V8 2022-06-08 2022-06-22
CVE-2018-6065 Google Chromium V8 2022-06-08 2022-06-22
CVE-2018-17480 Google Chromium V8 2022-06-08 2022-06-22
CVE-2017-5070 Google Chromium V8 2022-06-08 2022-06-22
CVE-2017-5030 Google Chromium V8 2022-06-08 2022-06-22
CVE-2018-17463 Google Chromium V8 2022-06-08 2022-06-22
CVE-2019-13720 Google Chrome WebAudio 2022-05-23 2022-06-13
CVE-2019-5786 Google Chrome Blink 2022-05-23 2022-06-13
CVE-2021-39793 Google Pixel 2022-04-11 2022-05-02
CVE-2022-1096 Google Chromium V8 2022-03-28 2022-04-18
CVE-2022-1364 Google Chromium V8 2022-04-15 2022-05-06
CVE-2022-0609 Google Chromium Animation 2022-02-15 2022-03-01
CVE-2021-30551 Google Chromium V8 2021-11-03 2021-11-17
CVE-2021-37975 Google Chromium V8 2021-11-03 2021-11-17
CVE-2020-6418 Google Chromium V8 2021-11-03 2022-05-03
← Prev Page 1 of 2 · 71 entries Next →

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