← CRA Glossary
CVD & Vulnerability Management

Critical Vulnerability

A critical vulnerability is a security flaw assigned a CVSS base score of 9.0 or higher, indicating the highest potential for harm - typically enabling remote code execution or full system compromise without authentication. Critical vulnerabilities require accelerated remediation and immediate advisory publication under CRA-compliant vulnerability handling processes.

A critical vulnerability is a security flaw assigned a CVSS base score of 9.0 or higher, indicating the highest potential for harm - typically enabling remote code execution or full system compromise without authentication. Critical vulnerabilities require accelerated remediation and immediate advisory publication under CRA-compliant vulnerability handling processes.

CVD & Vulnerability Management

Last updated 19 July 2026

What Is a Critical Vulnerability?

A critical vulnerability is a security flaw with a CVSS base score of 9.0 to 10.0 on the standard 0–10 severity scale. This score reflects the highest potential impact: vulnerabilities in this range typically allow an unauthenticated attacker to remotely execute arbitrary code, gain full administrative control, or cause complete denial of service with no user interaction required. Classic examples include buffer overflow vulnerabilities in network-facing services, authentication bypass flaws in administrative interfaces, and SQL injection vulnerabilities with full database access. Critical vulnerabilities in widely deployed products are priority targets for threat actors and are frequently weaponised within days of public disclosure, making rapid manufacturer response essential.

CRA reference:Annex I

CVSS and the Critical Severity Band

The CVSS (Common Vulnerability Scoring System) framework, published by FIRST, defines five severity bands: None (0.0), Low (0.1–3.9), Medium (4.0–6.9), High (7.0–8.9), and Critical (9.0–10.0). Achieving a Critical base score requires a combination of high impact ratings (confidentiality, integrity, and/or availability) with low attack complexity, no required privileges, and no user interaction - or equivalently, network accessibility combined with high impact and no mitigating factors. CVSS v4.0 introduced additional granularity including threat metrics and supplemental scores, but the base score critical threshold remains at 9.0. Manufacturers should note that a high CVSS base score does not always mean high contextual risk - environmental scoring can adjust the effective severity when compensating controls are in place.

CRA reference:Annex I

Critical Vulnerability Response Under the CRA

The CRA does not define 'critical' as a specific regulatory category but requires that vulnerabilities be addressed 'without undue delay' - language that industry interprets as requiring the fastest response for the highest-severity issues. For critical vulnerabilities, CRA-compliant manufacturers should:

  • Triage within 24–48 hours: Validate the vulnerability, confirm scope, and establish an EPSS-informed exploitation probability assessment.
  • Issue interim advisory within 5 days: Even before a patch is available, publish guidance on mitigations and workarounds.
  • Target patch release within 30 days: Compress the development and testing cycle, with emergency release approval processes bypassing normal sprint cadences.
  • Notify ENISA immediately if actively exploited: If evidence of exploitation exists, the 24-hour notification obligation applies regardless of patch status.
CRA reference:Article 13, Article 14, Annex I

Managing Critical Vulnerabilities in Dependencies

A significant proportion of critical vulnerabilities affecting products originate in third-party dependencies - open source libraries, commercial SDKs, or firmware components. Log4Shell (CVE-2021-44228, CVSS 10.0) is the canonical example: a single critical vulnerability in a widely used logging library that affected thousands of products across hundreds of manufacturers. For manufacturers subject to the CRA, this means maintaining a current SBOM is not optional - it is the prerequisite for rapid identification of affected products when critical upstream vulnerabilities are disclosed. Manufacturers should have a defined process for SBOM-based CVE correlation that can be executed within hours of a critical CVE being published, not days.

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

Is a CVSS 9.8 vulnerability always more dangerous than a CVSS 7.5 one?+

Not necessarily in context. CVSS base scores measure theoretical maximum impact under idealised conditions. A CVSS 9.8 vulnerability in a component that is network-isolated and not exposed to untrusted input may pose less real-world risk than a CVSS 7.5 vulnerability in an internet-facing authentication component being actively exploited. Manufacturers should use CVSS Environmental scores to adjust for their specific deployment context and use EPSS scores to supplement base scores with exploitation probability data.

How quickly should a manufacturer publish an advisory for a critical vulnerability?+

Best practice and ENISA's CVD Good Practice Guide both recommend publishing an advisory for critical vulnerabilities within 5–7 days of the fix being available. For actively exploited critical vulnerabilities, interim mitigation guidance should be published even before a fix is ready - typically within 48–72 hours of confirming exploitation. The advisory should include the CVE identifier, CVSS score, affected versions, fix version, and concrete mitigation steps.

What qualifies as a critical vulnerability for CRA notification purposes?+

The CRA does not use 'critical' as a defined notification category. Its notification obligation in Article 14 is triggered by 'active exploitation' rather than severity classification. However, a critical-severity vulnerability (CVSS 9.0+) that is confirmed as actively exploited triggers both the full Article 14 notification cascade and the manufacturer's own highest-priority response SLAs. Manufacturers should treat the combination of high CVSS score and active exploitation as the clearest mandatory-notification trigger.

Sector checklists covering Critical Vulnerability

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)).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)).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.

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 Critical Vulnerability fits into your complete CRA compliance programme.

View checklists →