← CRA Glossary
CVD & Vulnerability Management

European Vulnerability Database (EUVDB)

The European Vulnerability Database (EUVDB) is an EU-level vulnerability repository operated by ENISA under the Cyber Resilience Act. It aggregates vulnerability notifications from manufacturers, national CSIRTs, and security researchers, providing a centralised European counterpart to the US National Vulnerability Database.

The European Vulnerability Database (EUVDB) is an EU-level vulnerability repository operated by ENISA under the Cyber Resilience Act. It aggregates vulnerability notifications from manufacturers, national CSIRTs, and security researchers, providing a centralised European counterpart to the US National Vulnerability Database.

CVD & Vulnerability Management

Last updated 25 October 2026

What Is the European Vulnerability Database?

The European Vulnerability Database (EUVDB) is a centralised EU vulnerability registry established under Article 16 of the Cyber Resilience Act and operated by ENISA. It serves as the primary EU-level repository for vulnerability information about products with digital elements sold on the EU market. The EUVDB aggregates: vulnerability notifications submitted by manufacturers per CRA Article 14 obligations; reports from national CSIRTs; and information from other sources including CVE databases and security researchers. The database is intended to provide EU market participants, regulators, and the security community with a comprehensive view of the vulnerability landscape for EU-market products - complementing but not replacing the US NVD/CVE programme.

CRA reference:Article 16

Manufacturer Notification Obligations to EUVDB

CRA Article 14 requires manufacturers to notify ENISA (and, through ENISA, the EUVDB) when they become aware of an actively exploited vulnerability in their product. The early warning is due within 24 hours and the vulnerability notification within 72 hours of becoming aware of the active exploitation. The final report is due 14 days after a fix or mitigation is available, with the details of the vulnerability and the security update. After a fix is available, ENISA adds the vulnerability to the EUVDB in agreement with the manufacturer, under Article 17(5). Manufacturers must also report any severe incident that could affect the security of their product in the EU market, separate from individual vulnerability notifications. These obligations apply in addition to any NIS2 incident reporting obligations that may apply to the manufacturer as an operator.

CRA reference:Article 14

EUVDB vs NVD: How They Relate

The US National Vulnerability Database (NVD), operated by NIST and fed by the CVE programme, is the dominant global vulnerability reference. The EUVDB is designed to complement rather than replace the NVD/CVE system. The CRA explicitly states that ENISA shall cooperate with the CVE programme and other international vulnerability databases to avoid duplication. In practice, many vulnerabilities reported to the EUVDB will also be assigned CVE identifiers and appear in the NVD. The EUVDB adds EU-specific context: which products are on the EU market, which MSAs have been notified, and what remediation status has been reported by manufacturers operating under the CRA. Manufacturers should treat CRA notification as additional to, not a replacement for, CVE assignment.

CRA reference:Article 16, Article 14

Using the EUVDB for Compliance and Intelligence

Manufacturers can use the EUVDB proactively as a vulnerability intelligence source. By monitoring EUVDB entries for components used in their products (cross-referenced against their SBOM), manufacturers can identify upstream vulnerabilities they need to assess and potentially patch. The EUVDB also provides visibility into how competitors and component suppliers are handling their CRA obligations - a useful market intelligence tool. From a compliance perspective, the EUVDB serves as the primary record of a manufacturer's notification history. Manufacturers that have submitted timely and complete notifications demonstrate proactive compliance behaviour to MSAs. Gaps in notification history - vulnerabilities known to the industry but absent from the manufacturer's EUVDB submissions - may attract MSA attention.

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 the EUVDB publicly accessible?+

The CRA provides for a publicly accessible portion of the EUVDB containing non-sensitive vulnerability information, similar to the public NVD. Sensitive details - such as information about vulnerabilities that have not yet been patched or that relate to active law enforcement investigations - may be restricted to authorised parties including national CSIRTs and MSAs. The public interface is expected to be searchable by product, manufacturer, and CVE identifier.

Does the EUVDB assign its own vulnerability identifiers?+

The EUVDB coordinates with the CVE programme and is expected to use CVE identifiers as the primary reference for vulnerabilities rather than creating a separate EU-specific numbering system. ENISA has engaged with MITRE and CVE Numbering Authorities (CNAs) to ensure EU market vulnerabilities receive CVE identifiers that flow into both systems. Manufacturers reporting to the EUVDB should include any existing CVE identifier in their notification.

How does a manufacturer submit a notification to the EUVDB?+

ENISA operates the EUVDB submission portal where manufacturers can register and submit vulnerability notifications. The submission interface supports both manual entry and structured data formats including CSAF. For manufacturers using CVD Portal, the platform's CSAF advisory generation feature creates output that can be directly submitted to the EUVDB portal, minimising manual work and ensuring completeness of required fields.

Sector checklists covering European Vulnerability Database (EUVDB)

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

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 European Vulnerability Database (EUVDB) fits into your complete CRA compliance programme.

View checklists →