Two engineers at a desk reviewing code together on a large monitor

PSIRT & disclosure

ENISA's European Vulnerability Database (EUVD), and what NIS2 Article 12 requires

Last updated:

The European Vulnerability Database (EUVD), at euvd.enisa.europa.eu, is ENISA's answer to a specific legal requirement in the EU's NIS2 Directive — Article 12(2), which directs ENISA to develop and maintain a European vulnerability database: a central, EU-operated repository of vulnerability information, distinct from (and cross-referencing) the US-centric CVE Program, NVD and CISA's Known Exploited Vulnerabilities catalogue that most security teams already track. Per ENISA's own topic page, it went live on 13 May 2025 — independently corroborated by trade press reporting the same launch — and is free to use for anyone, not just EU entities.

Key takeaways

  • Article 12 of the NIS2 Directive sets two separate duties: paragraph 1 is about people handling vulnerability reports, paragraph 2 is about the database.
  • The EUVD republishes vulnerability records from several feeds and adds EU exploitation data on top.
  • Every EUVD record has its own identifier in the form EUVD-YYYY-NNNNN, and a CVE ID, where one exists, appears as an alias.
  • The EUVD has a public read-only API at euvdservices.enisa.europa.eu.

What does NIS2 Article 12 actually require?

Article 12 of the NIS2 Directive sets two separate duties: paragraph 1 is about people handling vulnerability reports, paragraph 2 is about the database. The Official Journal text of Article 12(2) reads: "ENISA shall develop and maintain, after consulting the Cooperation Group, a European vulnerability database." The same paragraph says entities, "regardless of whether they fall within the scope of this Directive," and their suppliers may "disclose and register, on a voluntary basis, publicly known vulnerabilities," and that "all stakeholders shall be provided access" to the database.

Article 12 Addressed to What the text requires
12(1) Each member state Designate one CSIRT as coordinator for coordinated vulnerability disclosure; let people report a vulnerability to it, anonymously on request
12(1), last sentence The coordinating CSIRTs Where a vulnerability "could have a significant impact on entities in more than one Member State," cooperate within the CSIRTs network "where appropriate"
12(2) ENISA Build and run the database; each entry covers (a) a description of the vulnerability, (b) the affected ICT products or services and the severity, (c) available patches or, failing that, mitigation guidance from authorities or CSIRTs

Recital 63 explains the reason: similar databases "are hosted and maintained by entities which are not established in the Union," and ENISA "should explore the possibility of close cooperation with the operators of the Common Vulnerabilities and Exposures (CVE) system." That is why the EUVD sits on top of CVE rather than replacing it. Our NIS2 Directive guide covers the rest of the directive, including the other tasks it gives ENISA.

What does the EUVD aggregate, and what are its three lists?

The EUVD republishes vulnerability records from several feeds and adds EU exploitation data on top. Per ENISA's Vulnerability Services page, it "aggregates, stores, enriches, and publishes known vulnerabilities for public use," built from advisories by EU CSIRTs and ICT vendors, the EU KEV Catalogue (exploitation confirmed by EU CSIRTs Network members and ENISA), CISA's KEV Catalog, and other threat data providers.

The EUVD front page shows three lists, matching the categories reported at launch: critical vulnerabilities, EU CSIRT coordinated vulnerabilities (records assigned by ENISA and European CSIRTs acting as CNAs), and exploited vulnerabilities. The exploited flag merges both KEV sources. In ENISA's KEV dump downloaded on 12 November 2026, 1,796 CVEs carried a KEV source: 1,714 from CISA KEV only, 66 from both, and 16 from the EU KEV Catalogue only. One of those 16 was a MikroTik RouterOS flaw, which shows why a device maker should not watch the US list alone.

How do EUVD IDs relate to CVE IDs?

Every EUVD record has its own identifier in the form EUVD-YYYY-NNNNN, and a CVE ID, where one exists, appears as an alias. The two numbers do not line up. ENISA's API documentation offers a daily CSV that maps one to the other; on 12 November 2026 it held 405,368 pairs. The sequence part differed in nearly all of them: CVE-2021-22555 is EUVD-2021-9696. Even the year can differ: CVE-2015-7501 is EUVD-2022-3799.

A single record returned by the API carries these fields:

Field What it holds
id The EUVD ID, for example EUVD-2021-9696
aliases CVE ID and other IDs, such as a GitHub Security Advisory (GHSA) ID
assigner The CNA that published the original record (for example Google, redhat, debian)
baseScore, baseScoreVersion, baseScoreVector CVSS score, version and vector as published by the source
epss FIRST EPSS value, shown as a percentage (0–100)
exploitedSince Date exploitation was first recorded by a KEV source
enisaIdProduct, enisaIdVendor, enisaIdAdvisory Product, vendor and advisory links

Store the EUVD ID next to the CVE ID in your own records; never derive one from the other.

Is ENISA a CVE Numbering Authority, or a Root?

Both. ENISA's own Vulnerability Services page says it "has been a CVE Numbering Authority (CNA) since January 2024" and can "assign CVE identifiers (CVE IDs) and publish CVE Records for vulnerabilities discovered by or reported to ENISA and EU CSIRTs." It is also a CVE Root: it recruits, onboards, trains and oversees new European CNAs within its scope and handles disputes. For a hardware company, that means a CVE for your product can come from ENISA, from a national CSIRT that is a CNA under the ENISA Root, or from your own CNA. Our CVE Numbering Authority (CNA) rules guide explains how scopes decide who assigns.

How do you query the EUVD API?

The EUVD has a public read-only API at euvdservices.enisa.europa.eu. Per the API documentation, every endpoint uses GET with "No authentication required."

Endpoint Returns
/api/enisaid?id= One record, looked up by EUVD ID or by a CVE ID
/api/search? Filtered search: vendor, product, fromScore/toScore, fromEpss/toEpss, exploited=true, date ranges, assigner; at most 100 records per request
/api/exploitedvulnerabilities, /api/criticalvulnerabilities, /api/lastvulnerabilities The front-page lists, at most 8 records each
/api/dump/cve-euvd-mapping Full CSV of euvd_id,cve_id pairs, updated daily at 07:00 UTC
/api/kev/dump Merged CISA KEV and EU KEV list as JSON, with a sources field per CVE, updated daily at 07:00 UTC

For a product team the two dumps do most of the work: download them once a day and join on CVE ID locally, instead of calling the search endpoint for each component.

Worked example: how does one firmware SBOM look up in the EUVD?

Synthetic example: the gateway, its SBOM and its versions are made up. The EUVD IDs, KEV sources and EPSS values are real records returned by the EUVD API on 12 November 2026.

A maker of an industrial Wi-Fi gateway has a firmware SBOM with three components that a scanner already matched to CVEs. The PSIRT adds the EU view in four steps:

  1. Download /api/dump/cve-euvd-mapping and /api/kev/dump.
  2. Join each matched CVE ID against the mapping file to get the EUVD ID.
  3. Join against the KEV dump to read the sources field.
  4. For each hit, call /api/enisaid?id=<CVE> once to read epss and exploitedSince.
Component (synthetic version) CVE EUVD ID KEV source EUVD epss
Linux kernel 5.4 (unpatched build) CVE-2021-22555 EUVD-2021-9696 cisa_kev 78.68
bash 4.2 CVE-2014-6271 EUVD-2014-6157 cisa_kev 100.0
Apache Commons Collections 3.2.1 (web admin app) CVE-2015-7501 EUVD-2022-3799 eukev_kev only 85.56

The third row is the reason to add the EUVD: a team checking only CISA KEV would see no exploitation flag for that library, while the EU KEV Catalogue records exploitation since 14 July 2025. The PSIRT then records both IDs in its advisory and ranks the fix with the same KEV and EPSS logic it already uses.

Who runs coordinated disclosure under Article 12(1)?

A national CSIRT does, one per member state. Article 12(1) makes the designated CSIRT "a trusted intermediary" between the person reporting a vulnerability and the manufacturer, with three listed tasks: "identifying and contacting the entities concerned," "assisting the natural or legal persons reporting a vulnerability," and "negotiating disclosure timelines and managing vulnerabilities that affect multiple entities." For cross-border cases, ENISA's page says that as Secretariat of the EU CSIRTs Network it supports these coordinators when a vulnerability may have a significant impact in more than one member state. For a manufacturer, this runs next to its own process under ISO/IEC 29147/30111 and its published vulnerability disclosure policy: a researcher may go to the CSIRT first, so the PSIRT inbox must accept contact from one.

Where does the EUVD sit next to CRA reporting?

The EUVD is where fixed vulnerabilities end up; Cyber Resilience Act reporting is how they start. Under CRA Article 17(5), once a security update or other mitigation is available, ENISA "shall, in agreement with the manufacturer," add a vulnerability notified under Article 14(1) or 15(1) to the European vulnerability database. CRA recital 34 lists checking that a component "is free from vulnerabilities registered in the European vulnerability database" as one possible due-diligence step when integrating third-party components.

Mechanism Legal basis Who acts Trigger
EUVD NIS2 Art. 12(2) ENISA publishes; anyone reads Publicly known vulnerability
CRA Single Reporting Platform CRA Art. 14, applies from 11 September 2026 per ENISA Manufacturer notifies Actively exploited vulnerability or severe incident in its own product
CSIRT designated as coordinator NIS2 Art. 12(1) National CSIRT A third party reports a vulnerability

See our CRA 24-hour reporting guide for the notification steps. Advisories published as CSAF with VEX are easier for CSIRTs and aggregators to reuse than PDF bulletins.

What are the common pitfalls?

  • Treating the EUVD number as the CVE number. The sequence and sometimes the year differ; always map through the CSV or the aliases field.
  • Reading EUVD EPSS on the wrong scale. The EUVD shows EPSS as 0–100; FIRST's own EPSS is a 0–1 probability. A filter of fromEpss=0.5 means 0.5 %, not 50 %.
  • Passing a list to vendor. The API documentation warns that vendor=Siemens,Schneider looks for one vendor whose name contains both words.
  • Replacing NVD with the EUVD. The EUVD republishes CVE data and adds EU exploitation; it is an extra source, not a substitute for the NVD record. Our NVD backlog and Vulnrichment guide covers gaps on that side.
  • Scraping the website. The front end is a JavaScript app; use the API and dumps instead.
  • Assuming registration is mandatory. NIS2 Article 12(2) describes voluntary disclosure and registration; CRA Article 17(5) adds notified vulnerabilities in agreement with the manufacturer.

How should a device maker start?

  1. Add the two daily EUVD dumps to your vulnerability intakenext to NVD, CISA KEV and EPSS, and store EUVD IDs alongside CVE IDs for every product finding.
  2. Flag EU-KEV-only entriesthat touch your firmware SBOM; they are the cases a US-only feed misses.
  3. Check whether ENISA or a national CSIRT is a CNA for your product area, so a CVE assigned outside your own CNA does not surprise you.
  4. Know your Article 12(1) coordinatorin each member state where you sell, and make sure your PSIRT accepts and logs contact from it.
  5. Keep CRA reporting, CSIRT coordination and EUVD publication as three tracked itemswith separate owners; the table above shows why they differ.

The FIRST PSIRT Services Framework covers how these intake and coordination duties fit into a PSIRT's service areas.

What does SoftWSP do with EUVD data?

Little directly, and this guide does not claim more. SoftWSP extracts an SBOM from firmware, writes it as CycloneDX 1.6 JSON, and matches components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories. It does not read the EUVD or the EU KEV Catalogue, so an EU-KEV-only entry like the third row above needs the extra join described here. The AI step drafts a cited report of the matches for an engineer to review; it does not assign CVE IDs, decide CVD coordination, or decide whether a finding triggers a CRA report. See PSIRT services for help running that intake.

Sources: NIS2 and CRA Official Journal texts, ENISA's EUVD and Vulnerability Services pages, and ENISA's EUVD API and data dumps (read 12 November 2026), with SecurityWeek and Cloud Security Alliance for launch context. This guide is not legal advice.

Put this guide to work

Frequently asked questions

What is the EUVD, and who runs it?

The European Vulnerability Database (EUVD) is a free, public vulnerability repository operated by ENISA, the EU Agency for Cybersecurity, at euvd.enisa.europa.eu. Per ENISA's own topic page, it provides "aggregated, reliable, and actionable information such as mitigation measures and exploitation status on cybersecurity vulnerabilities" affecting ICT products and services, intended for both national/EU authorities and the private sector. ENISA's own page is dated 13 May 2025, which independent reporting (SecurityWeek) corroborates as the database's public launch.

What legal requirement created the EUVD?

The NIS2 Directive — Directive (EU) 2022/2555 — requires it. A Cloud Security Alliance research note on the launch states the EUVD fulfils "a specific obligation imposed by NIS2 Article 12, paragraph 2," which directs ENISA to develop and maintain a European vulnerability database. The Official Journal text of Article 12(2) confirms it: "ENISA shall develop and maintain, after consulting the Cooperation Group, a European vulnerability database." Our [NIS2 Directive](/guides/nis2-directive-explained/) guide covers the directive's scope more broadly; its own ENISA-sourced summary describes the agency's vulnerability-registry role without citing Article 12 by number.

What does the EUVD actually publish, and how does it relate to CVE, NVD and CISA's KEV catalogue?

Per ENISA's vulnerability-disclosure topic page, the EUVD "aggregates, stores, enriches, and publishes known vulnerabilities for public use," drawing on advisories from EU CSIRTs and ICT vendors, an EU-maintained Known Exploited Vulnerabilities (KEV) catalogue synchronised into the EUVD, CISA's own KEV Catalog, and other threat-data providers. Independent reporting (SecurityWeek) describes three presented categories: critical vulnerabilities, EU-CSIRT-coordinated vulnerabilities, and exploited vulnerabilities, covering IT, OT and IoT products. The EUVD doesn't replace the global CVE Program — ENISA has itself been a CVE Numbering Authority (CNA) since 2024 per that same reporting, meaning it can assign CVE IDs directly rather than running a fully separate identifier scheme; see our [CVE Numbering Authority (CNA) rules](/guides/cve-numbering-authority-cna-rules/) guide for how CNA assignment works generally, and [KEV/EPSS vulnerability prioritization](/guides/kev-epss-vulnerability-prioritization/) for how the US CISA KEV catalogue the EUVD cross-references is used for prioritization.

What is the "CSIRT coordinator" role NIS2 Article 12 sets up, separately from the database itself?

Per a Cloud Security Alliance research note on NIS2 Article 12, the article requires each EU member state to designate a national CSIRT as a coordinated vulnerability disclosure (CVD) coordinator, responsible for "identifying and contacting affected entities," acting as intermediary between a reporter and the affected vendor, negotiating disclosure timelines, and managing multi-party disclosure scenarios; where a vulnerability could affect entities in more than one member state, the research note states the relevant national CSIRT coordinators "are required to cooperate within the European CSIRTs Network," with ENISA itself acting as a coordination point for cases that exceed a single member state's capacity. This CVD-coordinator role is a process obligation distinct from the EUVD database itself, and runs on a separate track from a manufacturer's own vulnerability disclosure process under standards like [ISO/IEC 29147/30111](/guides/cvd-process-iso-29147-30111/) or a published [vulnerability disclosure policy](/guides/vulnerability-disclosure-policy-template/).

Sources

  1. ENISA: European Vulnerability Database (EUVD) — official tool/topic page (purpose, intended audiences, dated 13 May 2025)
  2. ENISA: Vulnerability Services (topic page) — EUVD data sources (EU CSIRTs, ICT vendor advisories, EU KEV Catalogue, CISA KEV Catalog), ENISA's CVD coordination role
  3. SecurityWeek: EU Cybersecurity Agency ENISA Launches European Vulnerability Database (launch reporting, categories, ENISA's CNA role since 2024, named expert reactions)
  4. Cloud Security Alliance: ENISA Designated as EU CVE Root — Implications for NIS2 Compliance and Cross-Border Vulnerability Disclosure (NIS2 Article 12(2) legal-basis citation, national CSIRT coordinator role)
  5. EUR-Lex: Directive (EU) 2022/2555 (NIS2) — official consolidated text (Article 12 citation above cross-checked against secondary legal analysis)
  6. EUR-Lex: Regulation (EU) 2024/2847 (Cyber Resilience Act) — Article 17(5) and recital 34 on the European vulnerability database
  7. ENISA: EUVD API documentation (endpoints, parameters, daily CVE-to-EUVD mapping and KEV dumps; read 12 November 2026)
  8. ENISA: European Vulnerability Database (EUVD) front page (critical, EU CSIRT coordinated and exploited lists)
  9. FIRST: Exploit Prediction Scoring System (EPSS)
Was this guide helpful?

In this cluster

ENISA's European Vulnerability Database (EUVD), and what NIS2 Article 12 requires