# How CVSS, EPSS, and application context can guide vulnerability remediation

DevFeed: [How CVSS, EPSS, and application context can guide vulnerability remediation](<https://devfeed.tech/articles/knowing-which-vulnerability-to-fix-first-64821.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4229731/knowing-which-vulnerability-to-fix-first.html>)

Author: Sonu Kapoor

Published: 2026-10-05T09:00:00Z

Content type: article

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>)

Tags: [application-security](<https://devfeed.tech/tags/application-security.md>), [application-security-devops-devsecops-security-software-development](<https://devfeed.tech/tags/application-security-devops-devsecops-security-software-development.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [epss](<https://devfeed.tech/tags/epss.md>), [next](<https://devfeed.tech/tags/next.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

## AI overview

CVSS describes a vulnerability's technical severity, while EPSS estimates the likelihood of exploitation in the next 30 days. The article proposes combining these signals with reachability, exposure, and asset context to help developers prioritize dependency findings. Its CVE Lite CLI example uses four remediation lanes and treats the 90th EPSS percentile as a configurable default, not a universal threshold.

## Source excerpt

Common Vulnerability Scoring System (CVSS) severity tells you how serious a vulnerability could be. Exploit Prediction Scoring System (EPSS) estimates how likely exploitation is in the next 30 days. Neither one, by itself, tells you what your team should fix first. Run a dependency scan on any moderately sized JavaScript project and you will probably see a table of findings, many of them labeled "high" -- 10, 20, sometimes 50 entries. If they all carry the same label, which one gets the next hour of engineering time? The usual answer is the one with the highest CVSS number. That feels objective, but it uses a severity score as a remediation queue. Those are not the same thing. What CVSS actually measures The Common Vulnerability Scoring System describes technical severity. Its Base metrics account for characteristics such as attack vector, attack complexity, privileges required, user interaction, and potential impact on confidentiality, integrity, and availability. A high Base score means the vulnerability has a severe technical profile under the assumptions encoded by CVSS. It does not mean the vulnerable code is reachable in your application. It does not know whether the affected system is exposed to the internet, whether compensating controls exist, or whether exploitation is occurring. That distinction matters because severity is a property of a vulnerability. Priority is a decision about a vulnerability in context. Security teams have long added threat intelligence, exploit catalogs, asset data, and vendor-specific risk models to severity scores. But developer-time dependency scanners often collapse the result back into a single severity column. The developer sees an advisory ID and a label, then has to reconstruct the missing context. What EPSS adds The Exploit Prediction Scoring System, maintained by FIRST and updated daily, answers a different question. It estimates the probability that exploitation activity for a published CVE will be observed in the wild du