CVSS and EPSS: severity is not likelihood
CVSS versus EPSS · facts checked 2026-10-03
The facts
- CVSS, the Common Vulnerability Scoring System, rates the technical severity of a vulnerability on a scale from zero to ten. (FIRST)
- FIRST, which maintains CVSS, says the score measures severity and is not a measure of risk on its own. (FIRST)
- FIRST published version four of CVSS in November 2023. (FIRST)
- EPSS, the Exploit Prediction Scoring System, estimates the probability that a vulnerability will be exploited in the wild in the next thirty days. (FIRST)
- FIRST publishes updated EPSS scores for published CVEs every day. (FIRST)
The panel
Jordan Pike AI host
FIRST says CVSS, the Common Vulnerability Scoring System, rates the technical severity of a vulnerability on a scale from zero to ten, measures severity—not risk—on its own, and version four was published in November 2023.
Jordan Pike AI host
FIRST adds that EPSS, the Exploit Prediction Scoring System, estimates the probability a vulnerability will be exploited in the wild in the next thirty days, and the agency publishes updated EPSS scores for published CVEs every day.
Jordan Pike AI host
Your board wants to know which flaws could actually hit the bottom line, not just how nasty they look on paper. So ask your dev leads: do we track both CVSS and EPSS, and how do we turn those numbers into a patch schedule?
Maya Okafor AI analyst
CVSS gives you a severity snapshot—think of it as a fire alarm’s volume. EPSS is the weather forecast telling you if the fire is likely to start. Relying on the alarm alone can waste time on low-probability sparks. The fix is to treat both as complementary: map high-severity bugs to risk registers, and use EPSS to prioritize exploitation-likely items. This is another metric that should have died in 2004, but here it lives on.
Dex Moreno AI analyst
Attackers love a high EPSS. I'd give that a solid eight out of ten for elegance—quick, low-effort, high payoff. The target deserved better.
Jordan Pike AI host
Dex, we are not rating it out of ten.
Dex Moreno AI analyst
An attacker scans for public CVEs with a high EPSS number because that’s a green light that the community or a tool already has an exploit. The CVSS score matters less; a low-severity but high-EPSS flaw can give a foothold fast, letting the bad guy pivot to higher-value assets and steal credentials for lateral movement.
Maya Okafor AI analyst
While EPSS tells you what’s likely to be weaponised, you still need CVSS to understand the potential impact. Ignoring severity could blind the board to a flaw that, if exploited, would cripple critical services. So I’d argue you weight both, with EPSS driving the immediate sprint and CVSS shaping the long-term roadmap.
Dex Moreno AI analyst
I get that impact matters, but in the wild the attacker’s budget is limited. They chase the highest EPSS first, regardless of CVSS. If you wait for a high-severity patch that has a low EPSS, you’re giving them time to discover a better target. Prioritise the likelihood, then layer in severity for exposure calculations.
Jordan Pike AI host
Bottom line: pull the latest CVSS and EPSS scores for every open CVE, let EPSS drive your short-term triage and CVSS inform the business impact assessment, and get the patches or mitigations in place before the next EPSS update.





