PROGRAM GUIDE, read 10 Nov 2026
Rank by evidence of exploitation first, then by severity and asset context
Order the evidence by how direct it is
Three public signals answer three different questions. The CISA KEV catalog answers whether exploitation has been observed. EPSS answers how likely exploitation is in the next 30 days. CVSS answers how bad the flaw is if it is exploited. A ranking that mixes them without saying which question each answers cannot be defended.
The order below goes from the most direct evidence to the least. Each tier is a rule you can write down and show to an auditor. A CVE moves up a tier when new evidence arrives and never moves down without a recorded reason.
| Tier | Evidence | Source | Question it answers |
|---|---|---|---|
| 1 | Listed in KEV | CISA KEV catalog | Has exploitation in the wild been observed |
| 2 | EPSS at or above your threshold | FIRST EPSS, daily | How likely is exploitation in 30 days |
| 3 | CVSS base 9.0 or above, internet-facing | NVD or vendor CVSS | How severe is the flaw on its face |
| 4 | Everything else | Scanner output | Queue by SLA and asset criticality |
Why the tiers start with KEV
KEV is a list of facts. CISA's own FAQ gives three criteria for adding an entry: a CVE ID, clear remediation guidance and reliable evidence of exploitation in the wild. A listed CVE has been exploited. A CVSS 9.8 may never have been.
The KEV Lag Ledger (318 additions, 2025-11-10 to 2026-11-09) shows how the catalog behaves. The median time from NVD publication to KEV listing was 10.5 days, and 45.3% of additions were listed within 7 days. A tier 1 rule therefore fires quickly for most entries and late for a long tail: 17.3% were published more than a year before they were listed.
Where EPSS fits
EPSS covers the CVEs that KEV has not listed. FIRST describes it as the probability of exploitation in the wild within the next 30 days, published daily for every scored CVE. Use it to pull forward CVEs that have no KEV entry yet.
Choose the threshold from your own capacity, not from a vendor. FIRST states there is no universal threshold and that 0.10 is commonly cited but carries no special authority from EPSS. Write the number in your policy and the date you chose it.
What to do with CVSS
CVSS orders the work inside a tier. It does not choose the tier. In the ledger, 45.9% of KEV additions scored 9.0 or above, so a CVSS-only cut would have caught those and missed the 10.4% that scored below 7.
Keep the base score from NVD or the vendor and record which one you used. For a CVE with no exploitation evidence, a CVSS score of 9.0 or above on an internet-facing asset still belongs in tier 3 and gets a deadline.
Write the rule so someone else can rerun it
A prioritization rule is a function with inputs, a date and a result. Store the KEV flag, the EPSS probability and percentile with their score date, and the CVSS vector with its version. Rerun the rule on the same inputs and the same tier must come out.
The Signal Matrix on this site lists which of 13 profiled platforms expose each signal. KEV is exposed by 8 of them and EPSS by 7 on the evidence read on 2026-11-10. If your platform exposes neither, ingest both feeds yourself and keep the dated copies.
- Tier 1 SLA: set by policy, and by BOD 26-04 where it applies to you.
- Tier 2 SLA: longer than tier 1, shorter than tier 3, reviewed monthly against the daily EPSS change.
- Re-tier on every new KEV addition, since the catalog changes the answer for CVEs already in your backlog.
Check the rule against a year of listings
Before adopting the tiers, replay them on the ledger. Of the 318 additions, 45.9% scored 9.0 or above on CVSS, so a tier 3 rule alone would have caught nearly half on severity. The 10.4% below 7 would have reached the queue only through KEV, which is the argument for tier 1.
Replay also tests the EPSS tier. With a threshold of 0.10, the listing-day scores select 63 of the 260 additions that had a score (24.2%). That means roughly three of four exploited CVEs were below the line on the day CISA listed them. Tier 2 is a way to bring forward CVEs before listing, and it will not catch most of them.
Sources
- FIRST, EPSS frequently asked questions, read 10 Nov 2026
- CISA, BOD 22-01 (revoked), read 10 Nov 2026
- FIRST, CVSS v3.1 Specification Document, read 10 Nov 2026
Last reviewed 10 Nov 2026.