← CRA Glossary
CVD & Vulnerability Management

Vulnerability Handling

Vulnerability handling is the complete lifecycle process through which a manufacturer identifies, evaluates, remediates, and discloses security vulnerabilities in its products. Annex I Part II of the CRA makes robust vulnerability handling a mandatory ongoing obligation for all manufacturers of products with digital elements.

Vulnerability handling is the complete lifecycle process through which a manufacturer identifies, evaluates, remediates, and discloses security vulnerabilities in its products. Annex I Part II of the CRA makes robust vulnerability handling a mandatory ongoing obligation for all manufacturers of products with digital elements.

CVD & Vulnerability Management

Last updated 17 October 2026

What Is Vulnerability Handling?

Vulnerability handling encompasses the end-to-end set of processes a manufacturer uses to manage security weaknesses in its products from discovery through to user notification and remediation. ISO/IEC 30111 defines vulnerability handling (also called 'vulnerability management') as distinct from vulnerability disclosure - it covers the internal processes, whereas disclosure covers the external communication. Under the CRA, vulnerability handling includes: maintaining an SBOM to know what is in the product; monitoring for new CVEs affecting components; validating and triaging reported vulnerabilities; developing patches; publishing advisories; and reporting to regulators when exploitation is detected.

CRA reference:Annex I Part II, Article 13(8)

CRA Vulnerability Handling Requirements

Annex I Part II lists the vulnerability handling obligations that form part of the essential requirements:

  • Component identification - document all software and hardware components, including third-party and open-source (SBOM).
  • Proactive monitoring - continuously monitor for vulnerabilities in components; assess impact on the product.
  • Timely remediation - develop and release patches without undue delay; do not impose charges for security fixes.
  • CVD policy - publish and maintain an accessible coordinated vulnerability disclosure policy.
  • Advisory publication - inform affected users of vulnerabilities and remediation steps.
  • ENISA notification - notify ENISA and national CSIRTs of actively exploited vulnerabilities within 24 hours.
  • Support period commitment - document and communicate the period during which vulnerabilities will be handled.
CRA reference:Annex I Part II

The Vulnerability Handling Lifecycle

A CRA-compliant vulnerability handling lifecycle follows these stages:

  1. Discovery - vulnerability identified through internal testing, external researcher report, CVE monitoring, or threat intelligence.
  2. Triage - validate the report, assess severity (CVSS score), determine exploitability, and check for active exploitation.
  3. Notification - if actively exploited, notify ENISA/CSIRT within 24 hours. Request CVE ID.
  4. Remediation - develop and test a fix; document the root cause.
  5. Release - publish the patch through the product update mechanism, free of charge.
  6. Advisory - publish a CSAF security advisory with CVE reference, CVSS score, affected versions, and remediation instructions.
  7. Documentation - update technical documentation with the vulnerability record and advisory.
CRA reference:Annex I Part II, Article 14

Vulnerability Handling for Third-Party Components

A significant CRA compliance challenge is vulnerability handling for third-party and open-source components. Manufacturers are responsible for these components as if they were their own. Required processes include:

  • CVE feed monitoring - subscribe to NVD, vendor security bulletins, and sector-specific ISAC feeds; match new CVEs against the product SBOM.
  • Impact assessment - for each matching CVE, determine if the vulnerable code path is reachable in the product.
  • Upstream patch tracking - monitor upstream projects for security fixes; integrate them into the product's next release cycle.
  • VEX publication - for CVEs where the vulnerability is present in a component but not exploitable in the product's specific configuration, publish a VEX statement (via CSAF) to prevent unnecessary customer alarm.

The SBOM is the foundation that makes all of this tractable.

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 is the difference between vulnerability handling and vulnerability disclosure?+

Vulnerability handling (ISO/IEC 30111) refers to the internal organisational processes for receiving, investigating, and fixing vulnerabilities. Vulnerability disclosure (ISO/IEC 29147) refers to the process of communicating vulnerability information to affected parties - researchers, users, regulators, and the public. The CRA requires both: the Annex I Part II process requirements govern handling; the CVD policy requirement and Article 14 notification obligations govern disclosure. A mature programme integrates both.

How long must a manufacturer handle vulnerabilities in a product?+

The CRA requires vulnerability handling throughout the product's support period, which the manufacturer must define and publish. The support period must be proportionate to the expected use life of the product. There is no EU-mandated universal minimum, but for long-life products (industrial equipment, medical devices), regulators expect multi-year commitments. At end-of-life, the manufacturer must notify users in advance and cease collecting unnecessary personal data.

Can we outsource vulnerability handling to a third party?+

Manufacturers can engage managed security service providers or specialist firms to assist with elements of vulnerability handling - monitoring, triage, advisory drafting - but regulatory responsibility remains with the manufacturer. The manufacturer must retain oversight, maintain documented processes, and ensure that any third-party arrangement enables it to meet its CRA timelines (including the 24-hour ENISA notification). Outsourcing without governance creates compliance risk, not compliance cover.

Sector checklists covering Vulnerability Handling

Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.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.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.

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

View checklists →