← CRA Glossary
Security Standards & Frameworks

Common Vulnerability Scoring System (CVSS) - Full Guide

The Common Vulnerability Scoring System (CVSS) is the industry-standard framework for assessing and communicating the severity of software vulnerabilities using a numerical score from 0 to 10. CVSS scores are referenced throughout the CRA compliance ecosystem - in vulnerability advisories, SBOM tooling, CSAF documents, and PSIRT triage processes - and are the primary language for communicating vulnerability severity under the regulation.

The Common Vulnerability Scoring System (CVSS) is the industry-standard framework for assessing and communicating the severity of software vulnerabilities using a numerical score from 0 to 10. CVSS scores are referenced throughout the CRA compliance ecosystem - in vulnerability advisories, SBOM tooling, CSAF documents, and PSIRT triage processes - and are the primary language for communicating vulnerability severity under the regulation.

Security Standards & Frameworks

Last updated 19 July 2026

What Is CVSS and How Does It Work?

The Common Vulnerability Scoring System (CVSS), currently at version 4.0 (released 2023), is an open framework maintained by FIRST (Forum of Incident Response and Security Teams) for rating the severity of software security vulnerabilities. CVSS produces a numerical score from 0.0 to 10.0, mapped to qualitative ratings: None (0.0), Low (0.1–3.9), Medium (4.0–6.9), High (7.0–8.9), and Critical (9.0–10.0). The score is calculated from metric groups: Base metrics (intrinsic vulnerability characteristics, unchanged by context - attack vector, complexity, privileges required, user interaction, scope, and impact); Threat metrics (current exploit maturity); and Environmental metrics (product-specific deployment context and mitigations). The NVD publishes CVSS scores for all CVEs.

CRA reference:Article 13(3),

CVSS in the CRA Compliance Context

CVSS is the de facto severity communication standard for CRA compliance. The CRA requires manufacturers to address vulnerabilities and provide users with information about their severity. CVSS base scores, published in the NVD, provide the standardised language for severity communication that both manufacturers and users understand. CSAF security advisories include CVSS vector strings so that users and their vulnerability management tools can process severity programmatically. PSIRT teams use CVSS scores to prioritise remediation queues: Critical (9.0+) vulnerabilities typically trigger emergency patch procedures; High (7.0+) trigger expedited remediation. CVSS scores also inform the CRA's 'without undue delay' patching standard - higher severity implies shorter acceptable delay.

CRA reference:Article 13(3),

Using CVSS Correctly: Base, Threat, and Environmental Scores

Manufacturers and users frequently rely only on the CVSS Base score from the NVD - a common and important error. The Base score reflects the vulnerability's intrinsic severity in isolation, without accounting for whether exploits exist (Threat metrics) or whether the product's specific environment mitigates the risk (Environmental metrics). A CVSS 9.8 Base score for a vulnerability exploitable only via adjacent network access, on a product deployed on an isolated industrial network with no internet exposure, may have a far lower Environmental score after accounting for deployment context. Manufacturers should calculate Environmental scores for vulnerabilities affecting their products and use these adjusted scores in their own security advisories and remediation prioritisation - not rely solely on the NVD Base score.

CRA reference:Article 13(3)

Common Mistakes in CVSS Usage

The most frequent error is treating CVSS Base scores as absolute and definitive severity ratings. CVSS Base scores are designed to be a starting point for context-aware assessment, not the final word on risk. A second error is using outdated CVSS versions: the industry has largely moved to CVSS v3.1 and CVSS v4.0, but many older advisories and tools still reference CVSS v2 scores, which use a different scale and methodology. Manufacturers publishing CVSS scores in their security advisories should specify the CVSS version and include the full vector string, not just the numerical score, so recipients can audit and recalculate Environmental scores for their own context. Failing to include the vector string is a common advisory quality issue flagged by PSIRT communities.

CRA reference:Article 13(3)

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

What CVSS version should manufacturers use for CRA compliance?+

CVSS v3.1 remains the most widely used version and is supported by the NVD, CSAF tooling, and most vulnerability management platforms. CVSS v4.0, released in October 2023, introduces improvements including finer-grained attack complexity metrics and better support for OT/ICS environments. Manufacturers should use the latest version supported by their toolchain and specify the version and full vector string in all published advisories. Both v3.1 and v4.0 are acceptable for CRA compliance purposes; consistency within an advisory set is most important.

Is a CVSS score of 9.0 or above always a critical vulnerability requiring immediate patching?+

A CVSS Base score of 9.0+ indicates a critical severity vulnerability based on its intrinsic characteristics. However, the appropriate remediation timeline should be based on the Environmental score - which factors in the specific deployment context - combined with Threat metrics indicating whether an exploit exists. A CVSS 9.8 vulnerability that is only exploitable with physical access, on a product that is not physically accessible in its intended deployment, carries a much lower real-world risk than the Base score implies. Manufacturers should calculate and act on contextualised scores, not blindly apply a universal patching SLA based on Base scores alone.

Where should manufacturers publish CVSS scores for their products' vulnerabilities?+

CVSS scores should be included in all security advisories published by the manufacturer's PSIRT. The preferred format for machine-readable advisories is CSAF (Common Security Advisory Framework), which has dedicated fields for CVSS vector strings and score values. Human-readable advisories should include the CVSS version, numerical score, qualitative severity rating, and full vector string so that sophisticated users can audit the scoring and apply Environmental adjustments. CVSS data should also be included in any SBOM or VEX documents that reference specific CVEs.

Sector checklists covering Common Vulnerability Scoring System (CVSS) - Full Guide

Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Medical DevicesMedical devices regulated under the EU Medical Device Regulation (MDR) or In Vitro Diagnostic Regulation (IVDR) are generally excluded from the CRA. However, software products used in healthcare that are not classified as medical devices under MDR may fall within CRA scope. Manufacturers should carefully verify their product's regulatory classification.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Common Vulnerability Scoring System (CVSS) - Full Guide fits into your complete CRA compliance programme.

View checklists →