Practice

CVSS, EPSS, KEV: which vulnerabilities should I fix first?

By SBOMBox SBOM experts · · Updated · 3 min read

Short answer: fix anything on the CISA KEV list first, then anything with a high EPSS score, then sort the rest by CVSS and by whether the vulnerable code is reachable in your product. Record a VEX statement for everything you decide does not affect you.

Three signals, three different questions

CVSS, EPSS and KEV compared
SignalQuestion it answersScaleMaintained by
CISA KEVIs this being exploited right now?Listed or notCISA
EPSSHow likely is exploitation in the next 30 days?Probability 0 to 1, plus percentileFIRST
CVSSHow bad would it be if exploited?Score 0 to 10FIRST

Each signal alone misleads. Most CVEs rated critical by CVSS are never exploited, and a medium-severity flaw on KEV is more urgent than an unexploited critical one. The deep dives: what is CISA KEV and what is EPSS.

A simple order to work in

Check reachability before you patch

A finding is only real if the vulnerable code is in what you ship and can be reached. Before spending a sprint on an upgrade, check that the component is in the release SBOM rather than only in a test dependency, and whether the vulnerable function is called. The answer becomes your VEX justification.

Keep doing it, automatically

KEV changes several times a week and EPSS changes daily, so a triage done last month is already out of date. Store an SBOM per release and re-match it on a schedule. The free SBOM vulnerability scanner gives you a one-off view in your browser; SBOMBox re-checks every stored SBOM daily and puts KEV and high-EPSS findings at the top.

Frequently asked questions

Should I fix vulnerabilities by CVSS score?

Not by CVSS alone. CVSS measures severity, not likelihood. Put CISA KEV entries first and use EPSS to rank the rest, then use CVSS to judge impact.

What EPSS threshold should I use?

There is no standard. Start with the 90th percentile and adjust to your team's capacity.

What if a KEV vulnerability does not affect us?

Record a VEX 'not affected' statement with a justification, so customers and auditors can see the decision and the reason.