NIST Revises Vulnerability Management: Focus on High-Risk Issues

NIST is revising its vulnerability management, focusing on high-risk vulnerabilities.

NIST Revises Vulnerability Management: Focus on High-Risk Issues
NIST logo with cybersecurity symbol

The National Institute of Standards and Technology (NIST) has recently announced a significant change in how it manages the National Vulnerability Database (NVD). Faced with an exponential increase in vulnerability reports, NIST has decided to adopt a risk-based model, focusing detailed analysis only on the most critical vulnerabilities.

Rising number of vulnerability reports

Between 2020 and 2025, reports of Common Vulnerabilities and Exposures (CVEs) rose by 263%. This increase has put NIST under pressure: the agency enriched almost 42,000 CVEs in 2025, a 45% increase over the previous year. Despite these efforts, the agency has not been able to keep pace with the growing volume of reports.

New risk-based approach

To address this challenge, NIST has introduced a new risk-based triage model. Starting April 15, 2026, the agency will focus on enriching CVEs that meet specific criteria:

  • Vulnerabilities included in CISA's Known Exploited Vulnerabilities (KEV) Catalog: these CVEs will be enriched within one working day of receipt.
  • Vulnerabilities affecting software used within the federal government.
  • Vulnerabilities in critical software, as defined by Executive Order 14028.

CVEs that do not meet these criteria will still be listed in the NVD, but they will not automatically receive enrichment unless it is explicitly requested.

Implications for the cybersecurity community

This decision has raised concerns among cybersecurity experts. Ian Gray, vice president at Flashpoint, has stressed that reduced enrichment could create blind spots for companies, as many vulnerabilities may remain unanalyzed. In addition, Shane Fry, CTO of RunSafe Security, has highlighted the need for organizations to be more proactive in identifying the vulnerabilities that affect them, as NIST's approach could make it harder for companies and developers to keep their software up to date.

Conclusion

NIST's change to the CVE enrichment process is a direct response to the rising number of vulnerability reports. Although the risk-based approach allows the agency to focus on the most critical threats, it is essential for organizations to take proactive measures to identify and mitigate vulnerabilities, using a range of data sources and defense strategies to effectively address emerging threats.

  • Rising CVE reports: between 2020 and 2025, reports rose by 263%, putting NIST under pressure.
  • New risk-based model: NIST will focus on enriching critical CVEs, such as those in CISA's KEV catalog and in critical software.
  • Community concerns: experts fear that reduced enrichment could create blind spots for companies, requiring a more proactive approach to vulnerability management.