The National Institute of Standards and Technology (NIST) on Wednesday announced an update to its National Vulnerability Database (NVD) operations to better manage the current volume of new CVEs.
The update involves the adoption of a risk-based model for adding details to CVE entries, a process it has historically referred to as ‘enrichment’.
Until now, NIST has made efforts to enrich all CVE entries in the NVD, but the high flow of new CVEs is making this a difficult task, and the institute has been struggling for years to clear the growing backlog of submissions.
Moving forth, NIST will focus on enriching CVEs that have been added to CISA’s Known Exploited Vulnerabilities (KEV) catalog within one day of submission. Additionally, it will enrich entries for vulnerabilities in software used by federal agencies and in critical software defined by EO 14028.
“This change is driven by a surge in CVE submissions, which increased 263% between 2020 and 2025. We don’t expect this trend to let up anytime soon. Submissions during the first three months of 2026 are nearly one-third higher than the same period last year,” NIST says.
Last year, the institute enriched 42,000 CVEs, but it still lags behind the growing volume of submissions, and the new changes will allow it to focus on critical CVEs.
While new CVEs will still be added to NVD, they will be categorized as ‘Not Scheduled’ for enrichment, unless they meet the above criteria. However, users can request the addition of details for unscheduled CVEs via email.
“While CVEs that do not meet these criteria may have a significant impact on affected systems, they generally do not present the same level of systemic risk as those in the prioritized categories,” NIST notes.
The implementation of the new prioritization criteria will result in the backlog of unenriched CVEs published to the NVD before March 1, 2026, being moved to the Not Scheduled category.
Additionally, the institute will not provide its own severity score for CVEs that have a score submitted by their CVE Numbering Authority and will not reanalyze entries modified after enrichment unless the modifications materially impact the enrichment data.
CVE status labels and descriptions will also be updated, as NIST strives to better communicate CVE status and provide transparency on how it manages the current workload.
“We recognize that these changes will affect our users. However, this risk-based approach is necessary to manage the current surge in CVE submissions while we work to align our efforts with the needs of the NVD community. This shift also allows us to dedicate the resources required to develop the automated systems and workflow enhancements that will ensure the program’s long-term sustainability,” NIST says.
Related: NIST’s Quantum Breakthrough: Single Photons Produced on a Chip
Related: NIST Publishes Guide for Protecting ICS Against USB-Borne Threats
Related: Cyber Insights 2026: Information Sharing
Related: CVE and NVD – A Weak and Fractured Source of Vulnerability Truth
