CVSS Score Interpretation and Limitations
You'll learn what CVSS scores actually tell you, how to read severity ratings, and why a high CVSS score doesn't automatically mean you should patch immediately.
Understanding CVSS Severity Ratings
CVSS scores range from 0.0 to 10.0 and map to standardized severity levels:
- None (0.0): No vulnerability
- Low (0.1–3.9): Minimal impact or difficult to exploit
- Medium (4.0–6.9): Moderate impact with some complexity
- High (7.0–8.9): Severe impact, relatively easy exploitation
- Critical (9.0–10.0): Catastrophic impact, trivial exploitation
A CVSS 9.8 means the vulnerability has maximum impact on confidentiality, integrity, and availability, requires no privileges, needs no user interaction, and is exploitable remotely. But context matters enormously.
Why CVSS Alone Is Insufficient
Think of CVSS like a car's safety rating: a five-star crash-test score tells you the car is well-designed, but it doesn't tell you if your specific car has functional brakes, if you drive on icy roads, or if attackers are actively targeting your model.
CVSS limitations include:
- No exploitation context: A CVSS 10.0 in a service you don't run is irrelevant
- No threat intelligence: Doesn't indicate active exploitation in the wild
- No asset criticality: A medium-severity bug in your authentication server matters more than a critical bug in a test sandbox
- No compensating controls: Firewalls, network segmentation, and WAFs may mitigate risks CVSS doesn't account for
- Static scoring: Doesn't reflect evolving attacker interest or exploit availability
Key Takeaway: CVSS provides a standardized severity baseline, but effective prioritization requires combining CVSS with threat intelligence, asset criticality, exploitability data, and your organization's risk tolerance—never rely on the score alone.