Get fresh insights, pro tips, and thought starters–only the best of posts for you.
Common Vulnerability Scoring System, or CVSS, is an open framework used to rate the technical severity of cybersecurity vulnerabilities. It gives each vulnerability a numerical score, usually from 0.0 to 10.0, so security teams can compare vulnerabilities in a consistent way. It helps answer: How severe is this vulnerability from a technical standpoint? Security teams often use CVSS scores when reviewing CVEs, vulnerability scanner results, vendor advisories, and patch priorities.
CVSS scores come from different metrics that describe how a vulnerability can be exploited and what impact it may have. These metrics may look at factors such as attack complexity, required privileges, user interaction, and impact on confidentiality, integrity, and availability.
A higher score usually means a more severe vulnerability. For example:
| Score range | Severity |
|---|---|
| 0.0 | None |
| 0.1–3.9 | Low |
| 4.0–6.9 | Medium |
| 7.0–8.9 | High |
| 9.0–10.0 | Critical |
CVSS versions use metric groups to calculate or adjust severity. In CVSS v4.0, the main groups are:
CVSS helps teams communicate vulnerability severity clearly. Instead of relying only on vague terms like “serious” or “minor,” teams can use a standard scoring system to support triage and remediation planning.
It is useful for:
CVSS measures severity, not complete business risk. A vulnerability with a high score may not be exploitable in your environment, while a medium-score issue may be urgent if it affects a critical, internet-facing system. Teams should combine CVSS with asset importance, exploit availability, exposure, compensating controls, and business impact before deciding what to fix first.
CVSS helps teams understand vulnerability severity, but organizations still need visibility into where affected software exists. Hexnode UEM can help IT teams track device and app inventory, monitor compliance, and manage endpoint policies.
Hexnode XDR adds vulnerability management, threat investigation, and remediation support for endpoint risks. Meanwhile, Hexnode IdP can help limit access from risky or non-compliant devices using identity-aware controls such as SSO, MFA, RBAC, and device posture checks.
No. CVE identifies a known vulnerability, while CVSS rates the severity of that vulnerability using a standard scoring system.
Not always. Teams should also consider exposure, exploit activity, asset importance, and existing controls before prioritizing remediation.