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

URL: https://sbombox.com/blog/which-vulnerabilities-to-fix-first
By SBOMBox SBOM experts. Published 2026-10-06, updated 2026-11-17

> CVSS, EPSS or CISA KEV? How to combine the three signals to decide which vulnerabilities to fix first, with a simple order and thresholds.

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**

| Signal | Question it answers | Scale | Maintained by |
| --- | --- | --- | --- |
| CISA KEV | Is this being exploited right now? | Listed or not | CISA |
| EPSS | How likely is exploitation in the next 30 days? | Probability 0 to 1, plus percentile | FIRST |
| CVSS | How bad would it be if exploited? | Score 0 to 10 | FIRST |

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](https://sbombox.com/blog/what-is-cisa-kev) and [what is EPSS](https://sbombox.com/blog/what-is-epss).

## A simple order to work in

- 1. In KEV and in your product: fix or mitigate now. US federal agencies get a fixed due date for these; treat it as your ceiling. Under the CRA, confirmed active exploitation may also start a 24-hour reporting clock.
- 2. High EPSS: next. A common starting threshold is the 90th percentile; tune it so the volume matches what your team can fix each sprint.
- 3. High CVSS in code you actually use: schedule it into normal releases.
- 4. Everything else: batch it, and write a VEX 'not affected' statement with a justification where it does not apply.

## 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](https://sbombox.com/blog/what-is-vex).

## 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](https://sbombox.com/tools/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.
