Skip to content
StrikeCyberStrikeCyber
Field Manual · Concept

Known Exploited Vulnerabilities (KEV)

Reviewed 13 November 2026Concept 1 min read

Quick answer

The Known Exploited Vulnerabilities (KEV) catalogue is a public list maintained by the US Cybersecurity and Infrastructure Security Agency (CISA) of vulnerabilities confirmed as exploited in the wild, with a clear remediation action. It launched in 2021 and has become a widely used patching priority list worldwide.

On this page
01

What Qualifies

A vulnerability is added when it has a CVE identifier, there is reliable evidence of active exploitation, and there is clear remediation guidance such as a patch or mitigation. The catalogue also records whether the vulnerability is known to be used in ransomware campaigns.

02

Why It Matters

Only a small fraction of published vulnerabilities are ever exploited. KEV is a short, evidence-based list of the ones that are, which makes it one of the most useful inputs for prioritising patching anywhere in the world.

03

How to Use It

  1. Match KEV entries against your asset inventory, starting with internet-facing systems.
  2. Treat matches as urgent, and check for compromise if a system was exposed while unpatched.
  3. Track new additions daily. The Threat Radar does this, adding exploitation likelihood, ransomware links and practical check-and-fix guidance for each entry.
  4. Use it alongside CVSS and EPSS for everything else.
04

Regulatory and Framework Context

For Australian organisations, KEV complements ASD's ACSC alerts: the Threat Radar matches the two so you can see when ASD has warned about the same issue.

Being exploited now

Threat Radar →

The latest related vulnerabilities confirmed as exploited in the wild.

Latest intel on this topic

Updated hourly from the daily briefing. More in vulnerability news and security alerts.

Common questions

Is KEV only for US organisations?

No. The exploitation data is global, so it is useful anywhere. Only the binding deadlines apply specifically to US federal agencies.

How often is KEV updated?

Several times a week, whenever new exploitation is confirmed.

For testers: finding write-ups

How this shows up in a penetration test report, with severity, verification and remediation, in the StrikeOps Findings Library.

Change log

  1. 13 November 2026First published.
1300 654 898