Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is CVSS?

CVSS (Common Vulnerability Scoring System) rates the technical severity of vulnerabilities from 0.0 to 10.0. Learn how scores are built and why they are not the same as risk.

Home / Blog / Cybersecurity Terms / What Is CVSS?
17 November 2026

What Is CVSS?

What Is CVSS?

CVSS (Common Vulnerability Scoring System) is an open standard for rating the technical severity of software vulnerabilities on a scale from 0.0 to 10.0. It is maintained by FIRST, the Forum of Incident Response and Security Teams, and it is the number you see next to almost every CVE in advisories, scanner output, and penetration test reports. A CVSS score describes how bad a flaw is in principle; on its own, it does not tell you how urgently you need to fix it.

Versions in Use

CVSS v2 appeared in 2007, v3.0 in 2015, and v3.1 in June 2019. CVSS v4.0 was published on 1 November 2023. Many databases and tools still publish v3.1 scores while v4.0 adoption grows, and the two are not directly comparable, so always check which version a score uses before you rank findings side by side.

How a v3.1 Score Is Built

The Base score, which reflects the intrinsic characteristics of a vulnerability, comes from eight metrics:

MetricQuestion it answersValues
Attack Vector (AV)From where can it be exploited?Network, Adjacent, Local, Physical
Attack Complexity (AC)Are special conditions needed?Low, High
Privileges Required (PR)Must the attacker already have access?None, Low, High
User Interaction (UI)Does a victim need to do something?None, Required
Scope (S)Can the impact spread beyond the vulnerable component?Unchanged, Changed
Confidentiality, Integrity, Availability (C, I, A)What is the impact on each?None, Low, High

The result is written as a vector string. Log4Shell, for example, is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H—exploitable over the network, easy, needing no privileges or user interaction, with high impact across a changed scope—which calculates to the maximum 10.0.

Scores map to qualitative ratings:

Version 3.1 also defines optional Temporal metrics (exploit code maturity, remediation level, report confidence) and Environmental metrics that let you adjust the score for your own systems.

What Changed in CVSS v4.0

Base Scores Are Not Risk

The most common mistake is treating the Base score as a priority list. FIRST itself stresses that the Base score measures severity, not risk. A 9.8 on an isolated test server holding no sensitive data may matter less than a 6.5 on your internet-facing VPN that criminals are actively exploiting. Mature vulnerability management programmes add:

Scores can also differ between sources. A vendor, the NVD, and your scanner may each score the same CVE differently because they make different assumptions about configuration. Where you have better information about your own environment, use it.

Where CVSS Appears in Compliance

CVSS thresholds are written into several frameworks that UK organisations work with. Under PCI DSS, external scans by an Approved Scanning Vendor fail if any vulnerability scores 4.0 or higher. Cyber Essentials requires updates for vulnerabilities that the vendor rates “critical” or “high risk”, or that carry a CVSS v3 score of 7 or above, to be installed within 14 days of release. Many penetration test reports, including ours, use CVSS alongside a contextual risk rating that reflects how the finding could actually be exploited in your environment.

Turning thousands of scored findings into a short, defensible fix list is where most teams struggle. PMAP, our Pentest Management Platform, tracks findings, CVSS scores, and remediation status in one place.

FAQ – Frequently Asked Questions

What CVSS Score Counts as Critical?

In CVSS v3.x and v4.0, a score of 9.0 to 10.0 is rated Critical, 7.0 to 8.9 High, 4.0 to 6.9 Medium, and 0.1 to 3.9 Low, with 0.0 meaning None. These bands describe technical severity only. Your own prioritisation should also consider whether the flaw is being exploited, whether the affected system is exposed, and what data or services depend on it.

Why Do Different Sources Give the Same CVE Different Scores?

Scorers make different assumptions about default configurations, required privileges, or impact, and some score with CVSS v3.1 while others use v4.0. A vendor may know its product better than the NVD, while a scanner may simply reuse a published score. Check the vector string to see exactly what each source assumed, and adjust using your own environmental context where you can.

Should I Patch Everything Above 7.0 First?

A score threshold is a reasonable starting point, and Cyber Essentials uses 7.0 as its 14-day patching trigger. But a pure score-based queue wastes effort on unexploited flaws in internal systems while missing medium-rated bugs under active attack. Combine CVSS with exploitation data such as the CISA KEV catalogue and EPSS, plus asset exposure and criticality, to decide what goes first.

Should I Move to CVSS v4.0?

Start reading and recording v4.0 scores where vendors and tools provide them, because v4.0 describes modern vulnerabilities more precisely and separates threat information cleanly. Many sources still publish only v3.1, so most organisations will run both for some time. Keep the version alongside every score, and avoid mixing v3.1 and v4.0 numbers in a single ranking without noting the difference.

Related Terms

You May Be Interested In These

What Is Just-in-Time Access?

Cybersecurity Terms

17 November 2026

What Is Just-in-Time Access?

Read More
What Is DNS and How Does It Work?

Cybersecurity Terms

17 November 2026

What Is DNS and How Does It Work?

Read More