CVSS, EPSS and KEV: how to prioritise vulnerabilities
Updated 2026-11-17
Short answer
CVSS tells you how severe a vulnerability would be if exploited. EPSS estimates how likely it is to be exploited soon. KEV is a list of vulnerabilities that are already being exploited. Fix what is on KEV first, then what scores high on both EPSS and CVSS, and only if it applies to your image and can be reached.
What each one measures
- CVSS: severity, from 0 to 10, based on how the flaw can be attacked and its impact.
- EPSS: probability of exploitation in the near future.
- CISA KEV: a yes or no. It is being exploited in the wild.
Why CVSS alone is not enough
Many vulnerabilities score 9 or more and are never exploited, and some with a moderate score are used every day. Sorting by CVSS alone sends you to fix things in the wrong order.
An order that works
- Leave out what does not affect your version or does not apply to how the image is built.
- Fix anything on the KEV list.
- Then high EPSS with high CVSS, starting with what can be reached from the network.
- Then the rest, grouped by package so one update closes several.
How scancontainer does it
The report already combines these signals with whether each vulnerability applies and can be reached, and gives you the list in that order with the reason for each position.