At a glance
- Owner
- CVE Program, sponsored by CISA and operated by MITRE
- Version
- November 2026
- Applies to
- Anyone who tracks, reports or prioritises vulnerabilities
- Mandatory
- Not applicable
- Assessed by
- Not applicable
- Cost model
- Free
Key points
- A CVE ID is a unique public identifier for a disclosed vulnerability, such as CVE-2026-12345. It identifies; it does not score or prioritise.
- CVE IDs are assigned by CVE Numbering Authorities (CNAs), mostly vendors and coordinators, under the CVE Program, which is sponsored by CISA and operated by MITRE.
- NIST's National Vulnerability Database (NVD) adds analysis to CVE records. Since 15 April 2026 it enriches only priority CVEs, such as those in the CISA KEV catalogue, so many records now carry only the CNA's own data.
- The programme nearly lost its funding in April 2025. CISA's acting director has since said it is fully funded, and in March 2026 it was reported to have moved to a protected funding line.
- ENISA became a CVE Program Root in November 2025, and its European Vulnerability Database (EUVD) has operated since May 2025.
How a CVE record is made
- Discovery and report
A researcher, vendor or customer finds a vulnerability and reports it, usually to the vendor.
- Assignment
A CNA whose scope covers the product assigns a CVE ID. Vendors are usually CNAs for their own products; coordinators such as CERT/CC cover the rest.
- Publication
The CNA publishes the CVE record with a description, affected products and versions and references. Many CNAs also add a CVSS score and CWE.
- Enrichment
Downstream databases such as the NVD and EUVD add analysis, scores and product identifiers (CPE).
- Prioritisation data
Separate services add exploitation evidence (CISA KEV) and likelihood (EPSS).
Who does what
| Body | Role |
|---|---|
| CVE Program (MITRE, sponsored by CISA) | Runs the identifier system, the CVE List and the CNA network |
| Roots and Top Level Roots | Recruit, onboard and oversee CNAs in their scope; MITRE and CISA are Top Level Roots, and ENISA is a Root for organisations within its EU mandate |
| CNAs | Assign IDs and publish records for products in their scope |
| NIST NVD | Enriches records with CVSS, CWE and CPE for priority CVEs |
| ENISA EUVD | EU database aggregating CVE records with EU CSIRT information |
| CISA KEV | Flags CVEs with evidence of active exploitation |
| FIRST EPSS | Estimates the probability of exploitation in the next 30 days |
What changed in 2025 and 2026
Changes from Before April 2025 to November 2026
- Funding scare (April 2025): MITRE warned that its CVE contract would lapse; CISA extended the contract for 11 months hours before it lapsed. Board members formed the CVE Foundation to plan for an independent future.
- Funding secured (2026): the CVE Board was told at its January 2026 meeting that there would be no funding cliff in March, and CISA's acting director, Nick Andersen, said the programme is fully funded. Reporting in March 2026, citing unnamed sources, said it had moved to a protected funding line.
- NVD prioritisation (15 April 2026): citing a 263 per cent rise in submissions between 2020 and 2025, NIST now enriches CVEs in the KEV catalogue (aiming for one business day), CVEs for software used by the US federal government, and critical software. Others are labelled "Lowest Priority" and not scheduled for immediate enrichment. Backlogged CVEs published before 1 March 2026 move to "Not Scheduled". NIST no longer routinely adds its own score where the CNA has provided one.
- ENISA Root (November 2025): ENISA can now onboard and oversee CNAs within its mandate, and existing EU CNAs may move under it voluntarily.
- EUVD (May 2025): created under NIS2 Article 12. Early independent analysis (VulnCheck, May 2025) found tens of thousands of CVEs missing from its main API and less enrichment than the NVD, so do not rely on it as a single source.
- EU Cyber Resilience Act (from 11 September 2026): manufacturers must report actively exploited vulnerabilities in their products within 24 hours as an early warning, sent to the coordinating CSIRT and ENISA through ENISA's Single Reporting Platform.
Practitioner note
If your scanner or vulnerability management tool relies on NVD enrichment for CVSS scores or product matching, expect gaps for CVEs that NIST no longer prioritises. Check that the tool also reads the CNA's own data from the CVE record, and use KEV and EPSS for prioritisation rather than waiting for an NVD score.
Common mistakes
- Treating "no NVD score" as "low risk". Many recent CVEs now have only the CNA's score, or none.
- Searching only the NVD and missing vulnerabilities that are published on the CVE List but not yet enriched.
- Assuming every vulnerability has a CVE. Misconfigurations, many cloud service flaws and some vendor fixes never receive one.