EngineeringApril 23, 2026·2 min read

EPSS Is Better Than CVSS for Prioritising Vulnerabilities

A vulnerability with a CVSS score of 9.8 does not necessarily need to be fixed before a vulnerability with a CVSS score of 7.2. That surprises many teams, but it follows from what CVSS measures and what it leaves out.

What CVSS measures

The Common Vulnerability Scoring System (CVSS) measures the severity of a vulnerability from its technical characteristics: attack vector, complexity, privileges required, user interaction, and impact on confidentiality, integrity and availability. A CVSS 9.8 means the vulnerability is remotely exploitable, requires no authentication, and has high impact on all three.

What a CVSS base score does not measure is whether anyone is exploiting the vulnerability in the wild.

What EPSS measures

The Exploit Prediction Scoring System (EPSS), published by FIRST.org, estimates the probability that exploitation activity for a CVE will be observed in the next 30 days. It is a statistical model trained on observed exploitation and on signals such as the availability of public exploit code, and its scores are recalculated daily.

An EPSS score of 0.45 means the model gives a 45% probability that the vulnerability will be exploited somewhere in the next 30 days. That is time-bound and based on attacker behaviour. It is also a statement about the internet as a whole and not about your systems, so it does not replace knowing which of your assets are exposed.

The practical difference

Consider two findings.

Finding A: CVSS 9.8, EPSS 0.001 (0.1% exploitation probability). A deserialisation vulnerability in a library used only in an internal admin tool behind VPN and SSO.

Finding B: CVSS 7.2, EPSS 0.42 (42% exploitation probability). A path traversal vulnerability in a public-facing API endpoint, with proof-of-concept exploit code circulating publicly.

If you prioritise by CVSS, you fix Finding A first. If you prioritise by EPSS and exposure, you fix Finding B first, and Finding B is the one more likely to be used against you this month.

EPSS only exists for vulnerabilities with a CVE identifier. A flaw in your own code has no EPSS score, and for those severity and exposure remain the guide. The CISA Known Exploited Vulnerabilities catalogue is the other signal worth using: a CVE on that list has already been exploited, which outranks any forecast.

Spoorder's priority score combines CISA KEV listing, severity, EPSS and a reachability bonus, and sorts findings into Fix now, Fix soon and Watch.

Ready to scan your application?

Free health check: HTTPS, TLS and security headers for one URL, in about a minute. Free account, no credit card.

Scan your app free →
← Back to blog