← CRA Glossary
Security Standards & Frameworks

National Vulnerability Database (NVD)

The National Vulnerability Database (NVD) is the US government's comprehensive repository of CVE records enriched with CVSS severity scores, CWE classifications, and CPE product identifiers, maintained by NIST. It is the primary machine-readable vulnerability intelligence source used by SCA tools and vulnerability scanners globally, including by EU manufacturers complying with the CRA.

The National Vulnerability Database (NVD) is the US government's comprehensive repository of CVE records enriched with CVSS severity scores, CWE classifications, and CPE product identifiers, maintained by NIST. It is the primary machine-readable vulnerability intelligence source used by SCA tools and vulnerability scanners globally, including by EU manufacturers complying with the CRA.

Security Standards & Frameworks

Last updated 19 July 2026

What Is the National Vulnerability Database?

The National Vulnerability Database (NVD), maintained by the US National Institute of Standards and Technology (NIST), is the world's most widely used vulnerability intelligence repository. It builds on the CVE list maintained by MITRE, enriching each CVE entry with: a CVSS v3.x base score and vector string for severity assessment; Common Weakness Enumeration (CWE) classifications identifying the underlying software flaw type; Common Platform Enumeration (CPE) product identifiers for machine-matching against affected products; and reference links to vendor advisories and proof-of-concept resources. NVD data is freely available via a public API and is the primary data source for most commercial and open-source vulnerability management tools.

CRA reference:Article 13(3)(5)

Why the NVD Is Relevant to CRA Compliance

The CRA requires manufacturers to monitor for vulnerabilities in their products and components and to address them without undue delay. The NVD is the global reference database that most vulnerability scanning and SCA tools use to identify known vulnerabilities in software components. For EU manufacturers, maintaining a subscription to NVD data feeds - either directly via the NIST API or via tools that consume it - is the practical foundation of any vulnerability monitoring programme. CVSS scores from the NVD also provide the standardised severity ratings that manufacturers should use to prioritise remediation and to communicate vulnerability severity to users in security advisories.

CRA reference:Article 13(3),

How Manufacturers Use the NVD

Manufacturers integrate NVD data into their vulnerability management workflow in several ways: (1) SCA tools query the NVD API to match components in a product's SBOM against known CVEs; (2) vulnerability scanners use NVD data to identify unpatched software versions; (3) PSIRT teams use NVD CVSS scores to prioritise remediation effort; (4) security advisories reference NVD CVE identifiers to provide users with standardised identifiers for vulnerabilities being addressed; and (5) CSAF advisories include NVD-sourced CVSS data to convey severity. The NVD's CPE dictionary helps automate the matching of disclosed vulnerabilities to specific product versions in the manufacturer's SBOM.

CRA reference:Article 13(3)(5)

Common Mistakes

Manufacturers relying solely on the NVD may miss vulnerabilities that are disclosed in vendor advisories or GitHub Security Advisories (GHSA) before NVD analysis is complete - NVD enrichment can lag CVE publication by days or weeks. The NVD backlog issues experienced in 2024 highlighted this risk. Manufacturers should supplement NVD monitoring with the OSV (Open Source Vulnerabilities) database and direct vendor advisory subscriptions for critical components. Another error is treating NVD CVSS base scores as definitive severity ratings without adjusting them with environmental and temporal metrics that reflect the product's specific deployment context.

CRA reference:Article 13(3)

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 NVD a European database and does it cover EU-relevant vulnerabilities?+

The NVD is a US government database maintained by NIST, but it is a global resource covering vulnerabilities in software and hardware products used worldwide. ENISA and the European Commission reference NVD CVE data in their guidance materials. EU manufacturers should use the NVD as a primary vulnerability intelligence source, supplemented by ENISA's own vulnerability resources, the OSV database for open-source components, and relevant national CSIRT advisories.

How does the NVD relate to the CVE list?+

The CVE (Common Vulnerabilities and Exposures) list, maintained by MITRE and administered through CVE Numbering Authorities (CNAs), is the authoritative identifier system for publicly disclosed vulnerabilities. The NVD takes CVE records from MITRE and enriches them with CVSS severity scores, CWE classifications, CPE product mappings, and reference links. The CVE list provides the identifiers; the NVD provides the enriched analytical data that makes those identifiers actionable for vulnerability management.

What should manufacturers do when the NVD has not yet scored a newly published CVE?+

There is frequently a lag between CVE publication on the MITRE list and the NVD completing its analysis and assigning a CVSS score. Manufacturers should not wait for NVD enrichment before beginning vulnerability assessment. If a CVE affects a component in a shipped product, manufacturers should conduct their own preliminary severity assessment using the available description, vendor advisory, and CVSS calculator - and initiate triage immediately. Waiting for NVD completion before acting can cause manufacturers to exceed the CRA's 'without undue delay' remediation standard.

Sector checklists covering National Vulnerability Database (NVD)

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

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

View checklists →