← CRA Glossary
CVD & Vulnerability Management

CVSS v4.0

CVSS v4.0 is the fourth major version of the Common Vulnerability Scoring System, published by FIRST in November 2023. It introduces significant changes to the scoring model including more granular base metrics, new supplemental score groups, and improved handling of OT/ICS and IoT vulnerability contexts - areas directly relevant to CRA-covered products.

CVSS v4.0 is the fourth major version of the Common Vulnerability Scoring System, published by FIRST in November 2023. It introduces significant changes to the scoring model including more granular base metrics, new supplemental score groups, and improved handling of OT/ICS and IoT vulnerability contexts - areas directly relevant to CRA-covered products.

CVD & Vulnerability Management

Last updated 26 October 2026

What Is CVSS v4.0?

CVSS v4.0 is the latest major release of the Common Vulnerability Scoring System, the industry-standard framework for communicating the characteristics and severity of software vulnerabilities. Published by FIRST in November 2023, CVSS v4.0 significantly revises the metric structure of its predecessor (v3.1), which had been in use since 2019. Key structural changes include: renaming and redefining several base metrics; introducing new 'supplemental' metrics for additional context (such as Safety and Automatable); separating 'threat' (exploitation status) into its own dedicated metric group; and restructuring the temporal metrics. The result is a more expressive and contextually accurate scoring system.

CRA reference:Annex I

Key Changes in CVSS v4.0 Relevant to CRA Products

Several CVSS v4.0 changes are particularly relevant to manufacturers of CRA-covered products:

  • Safety (S) supplemental metric: CVSS v4.0 introduces a Safety metric indicating whether exploitation of the vulnerability could have physical safety consequences. This is directly relevant for products used in safety-critical contexts, such as industrial controllers.
  • Automatable (AU) metric: Indicates whether the vulnerability can be exploited at scale without human interaction - a key factor for IoT products that may be targeted by automated botnets.
  • Improved OT/ICS context: v4.0 provides clearer guidance for scoring vulnerabilities in operational technology and industrial control systems contexts.
  • Threat metrics separate from base: The new structure cleanly separates 'what this vulnerability can do' (base) from 'whether it is being actively exploited' (threat) - cleaner than v3.1's temporal metrics.
CRA reference:Annex I

CVSS v4.0 Score Nomenclature

CVSS v4.0 uses a new naming convention for combined scores to avoid confusion with v3.x:

  • CVSS-B: Base score only - the theoretical maximum severity.
  • CVSS-BT: Base + Threat metrics - accounts for exploitation status.
  • CVSS-BE: Base + Environmental metrics - accounts for deployment context (compensating controls, impact on specific system).
  • CVSS-BTE: Base + Threat + Environmental - the most complete, contextualised score.

For CRA vulnerability advisories, manufacturers should use at minimum CVSS-BT (including threat status) when publishing CSAF advisories, as this communicates exploitation status to users. When the manufacturer has information about typical deployment environments (e.g., the product is typically deployed behind a firewall), using CVSS-BE to provide an adjusted score helps users with their own risk assessments.

CRA reference:Annex I

Adopting CVSS v4.0 in PSIRT and Advisory Processes

CVSS v4.0 and v3.1 will coexist for several years during the transition period. CSAF (Common Security Advisory Framework) supports both versions. NVD is progressively adding v4.0 scores to new CVE entries while maintaining v3.1 scores for backwards compatibility. For manufacturers:

  • Existing advisories: No immediate need to re-score historical advisories in v4.0.
  • New advisories: Consider publishing both v3.1 and v4.0 scores during the transition to support tools not yet updated for v4.0.
  • PSIRT scoring guidelines: Update internal scoring guidelines to incorporate v4.0 supplemental metrics, particularly Safety and Automatable, for product categories where these are relevant.
  • Training: PSIRT team members should complete FIRST's CVSS v4.0 training to understand the scoring differences, particularly for the restructured attack complexity and privilege requirements metrics.

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

Should manufacturers switch to CVSS v4.0 immediately for CRA compliance?+

The CRA does not mandate a specific CVSS version. CVSS v3.1 remains fully adequate for CRA compliance. CVSS v4.0 provides meaningful improvements for IoT and OT product manufacturers through its supplemental metrics, so manufacturers of these product types should plan adoption. During the transition period, publishing both v3.1 and v4.0 scores in CSAF advisories is the recommended approach to maintain compatibility with tools that have not yet updated to v4.0.

How do CVSS v3.1 and v4.0 scores compare numerically?+

CVSS v4.0 scores are not directly comparable to v3.1 scores - they use different formulas and metric structures. A vulnerability that scores 9.8 in v3.1 may score differently in v4.0 depending on the new metric values. When transitioning, manufacturers should re-evaluate their existing vulnerability inventory rather than assuming numeric equivalence. FIRST provides a CVSS v4.0 calculator at first.org/cvss/v4-0 for score verification.

What is the 'Safety' supplemental metric in CVSS v4.0?+

The Safety (S) supplemental metric in CVSS v4.0 indicates the potential physical safety impact of exploiting a vulnerability. Values are: Negligible (no physical safety impact) and Present (potential physical harm to humans). This metric does not affect the numeric base score but provides critical context for manufacturers and users of safety-critical products. For CRA-covered products deployed in safety-relevant contexts - medical devices, industrial machinery, vehicles - reporting this metric in advisories provides important information for users conducting their own risk assessments.

Sector checklists covering CVSS v4.0

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.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.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)).IoT Sensors & Connected DevicesIoT sensors - temperature, humidity, pressure, flow, and motion sensors - are the backbone of industrial and building automation. Most fall into the Default CRA class, but their constrained hardware often makes meeting Annex I security requirements challenging. Manufacturers must plan for secure update mechanisms even on resource-constrained devices.

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 CVSS v4.0 fits into your complete CRA compliance programme.

View checklists →