# What is EPSS? The Exploit Prediction Scoring System, explained

URL: https://sbombox.com/blog/what-is-epss
By SBOMBox SBOM experts. Published 2026-11-17

> EPSS estimates the chance a vulnerability is exploited in the next 30 days. How to read the score and percentile, how it differs from CVSS, with KEV.

Short answer: EPSS, the Exploit Prediction Scoring System, gives every published CVE a probability between 0 and 1 that it will be exploited in the next 30 days. It is free, updated daily and run by FIRST, the same body that maintains CVSS. Use it to decide which of hundreds of 'critical' findings to fix first.

## Why EPSS exists

CVSS tells you how bad a vulnerability would be if exploited. It does not tell you how likely that is. Most CVEs are never exploited, so patching by CVSS alone means spending most of your time on flaws nobody attacks. EPSS adds the missing likelihood, using a model trained on observed exploitation activity, published exploit code and the properties of each CVE.

> The Exploit Prediction Scoring System (EPSS) is a data-driven effort for estimating the likelihood (probability) that a software vulnerability will be exploited in the wild.
>
> — FIRST, EPSS overview. [first.org/epss](https://www.first.org/epss/)

## How to read an EPSS score

Every CVE gets two numbers:

- Score: the probability of exploitation activity in the next 30 days, from 0 to 1. A score of 0.42 means a 42% chance.
- Percentile: the share of all scored CVEs with the same or a lower score. A percentile of 0.97 means the CVE is riskier than 97% of all others.

Scores are low for most CVEs and climb sharply for a small number, so the percentile is often easier to set thresholds on. Scores change daily as new evidence arrives, so read today's score, not the one from when you triaged.

```bash
# Look up today's EPSS score for a CVE (free, no key needed)
curl -s "https://api.first.org/data/v1/epss?cve=CVE-2021-44228" | jq '.data[0]'
```

## EPSS vs CVSS vs KEV

**How the three signals differ**

|  | EPSS | CVSS | CISA KEV |
| --- | --- | --- | --- |
| Measures | Likelihood of exploitation in 30 days | Severity if exploited | Confirmed exploitation |
| Output | Probability 0 to 1, plus percentile | Score 0 to 10 | Listed or not listed |
| Changes | Daily | Rarely, after publication | When CISA adds an entry |
| Maintained by | FIRST | FIRST | CISA |
| Best use | Rank the long tail | Judge impact | Fix first, no debate |

They answer different questions, so use all three. KEV says 'this is happening'. EPSS says 'this is likely to happen'. CVSS says 'this would hurt'. The [CISA KEV guide](https://sbombox.com/blog/what-is-cisa-kev) explains the first signal in detail.

## Using EPSS with your SBOM

- 1. Generate an SBOM per release and match it against vulnerability data. The [free SBOM vulnerability scanner](https://sbombox.com/tools/sbom-vulnerability-scanner) shows the CVEs for any CycloneDX or SPDX file.
- 2. Fix anything on KEV first.
- 3. Next, fix anything above your EPSS threshold. Many teams start at a percentile of 0.9 or a score of 0.1, then tune it to their capacity.
- 4. Sort the rest by CVSS and by whether the vulnerable code is reachable in your product.
- 5. Record a [VEX statement](https://sbombox.com/blog/what-is-vex) for every vulnerability you decide does not affect you, so the decision survives the next audit.

SBOMBox does steps 2 and 3 for every stored SBOM, every day, and shows the KEV and EPSS signals next to each finding. See [which vulnerabilities to fix first](https://sbombox.com/blog/which-vulnerabilities-to-fix-first) for the full method.

## Limits of EPSS

- It scores CVEs, not your product. A high score does not mean the vulnerable function is used in your build.
- It predicts exploitation attempts anywhere on the internet, not against you specifically.
- New CVEs can start with a low score that jumps once exploit code is published. Re-check, do not triage once.
- It does not cover vulnerabilities without a CVE ID, such as some ecosystem-only advisories.

## Frequently asked questions

### What does EPSS stand for?

Exploit Prediction Scoring System. It is maintained by FIRST, the Forum of Incident Response and Security Teams.

### What is a good EPSS score threshold?

There is no universal one. A common starting point is to prioritise CVEs above the 90th percentile, then adjust so the number of findings matches what your team can fix each sprint.

### How often is EPSS updated?

Daily. FIRST publishes new scores for every CVE each day, and scores can move sharply when exploit code appears.

### Is EPSS free?

Yes. The scores, the daily CSV and the API at api.first.org are free to use.

### Should I use EPSS instead of CVSS?

No, use both. EPSS estimates likelihood and CVSS estimates impact. Combine them with CISA KEV, which confirms exploitation.
