Reading a CVSS Score
what that 9.8 actually tells you, and what it leaves out
The Common Vulnerability Scoring System (CVSS) gives a vulnerability a score from 0.0 to 10.0 so people can describe how severe it is in a common way. It is maintained by FIRST, and you will see it on almost every vulnerability advisory.[1]
The severity bands
| Score | Rating |
|---|---|
| 0.0 | None |
| 0.1 to 3.9 | Low |
| 4.0 to 6.9 | Medium |
| 7.0 to 8.9 | High |
| 9.0 to 10.0 | Critical |
What goes into the base score
The base score describes the flaw itself, assuming nothing about your environment. In CVSS v3.1 the main factors are:
- Attack vector: can it be exploited over the network, or only locally or with physical access?
- Attack complexity: does exploitation need special conditions?
- Privileges required: does the attacker already need an account?
- User interaction: does someone have to click something?
- Scope: does it let the attacker affect things beyond the vulnerable component?
- Impact on confidentiality, integrity and availability.
That is how a score of 9.8 arises: reachable over the network, easy, no login, no user action and high impact on all three. CVSS v4.0 refines this (it adds an attack requirements metric and separates impact on the vulnerable system from impact beyond it) and names its scores by which metrics were used, such as CVSS-B for base only. Both versions are in use, so check which one an advisory quotes.
What a base score leaves out
CVSS measures severity, not risk to you. It does not know:
- Whether the system is exposed to the internet or buried deep inside.
- How valuable the affected asset is.
- Whether anyone is actually exploiting it yet.
- Whether you already have other controls in place.
Pair it with other signals
- EPSS estimates the probability that a vulnerability will be exploited in the wild soon.[2]
- CISA's KEV catalog lists vulnerabilities known to be exploited right now.[3] If it is on that list, treat it as urgent.
- Asset criticality and exposure: internet-facing, business-critical systems first.
- Compensating controls and whether a fix or workaround exists.
A sensible rule: use CVSS to sort, then use exploitation evidence and your context to decide.
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.