CVSS — Common Vulnerability Scoring System

Industry standard
Definition

CVSS (Common Vulnerability Scoring System) is a numerical score from 0.0 to 10.0 that describes the severity of a security vulnerability. A score of 10.0 is the worst possible. The score is calculated from factors like how easily the vulnerability can be exploited, whether the attacker needs authentication, and what the potential impact is.

What the scores mean

What goes into a CVSS score

The score is calculated from three metric groups:

Most tools only show the Base score. A CVSS 9.8 means: network-accessible, low complexity, no privileges needed, no user interaction, critical impact. That's about as bad as it gets.

The problem with only looking at CVSS

Not all High severity CVEs are equal in practice. A High CVE in a package you use in a code path that handles untrusted network input is far more dangerous than a High CVE in a package you only use in a build script. CVSS describes the vulnerability in isolation — it doesn't know your specific usage.

CISA KEV is a better signal for prioritization: it only lists vulnerabilities that are being actively exploited in the real world, regardless of CVSS score.

Check your dependencies for CVEs, CISA KEV entries, and supply chain risks.

Open PackageFix →

Free · No signup · No CLI · Runs in your browser

Common questions

Should I fix all High and Critical CVEs immediately?
All Critical CVEs should be fixed as fast as possible. For High CVEs, prioritize those on the CISA KEV catalog (actively exploited) first, then the rest on your normal patch schedule. Medium and Low CVEs can usually wait for the next scheduled update.
Can a Low CVSS score still be dangerous?
Yes — in the right context. A Low or Medium CVE in a package that handles authentication, cryptography, or sensitive data can be more dangerous than a High CVE in a logging utility. CVSS is a starting point, not the whole story.
What CVSS score does PackageFix show?
PackageFix shows severity badges (CRITICAL, HIGH, MEDIUM) derived from CVSS scores. Packages on the CISA KEV catalog get an additional 🔴 KEV flag regardless of their CVSS score, since active exploitation is more urgent than theoretical severity.
Why do different tools show different CVSS scores for the same CVE?
CVSS scores can differ between NVD, GitHub Advisory Database, and vendor advisories. Each may calculate slightly different base scores. Tools that use different data sources may show different numbers. The general severity tier (Critical/High/Medium) is usually consistent even when exact scores differ.

Related guides