Skip to content
Tech News
← Back to articles

NIST to stop rating non-priority flaws due to volume increase

read original get NIST Cybersecurity Framework Guide → more articles
Why This Matters

NIST's decision to stop assigning severity scores to low-priority vulnerabilities reflects the growing challenge of managing an exponential increase in vulnerability submissions. This shift aims to focus resources on the most critical security issues, enhancing overall cybersecurity efforts for both industry and consumers. By prioritizing high-impact vulnerabilities, the tech industry can better allocate mitigation efforts and improve security posture.

Key Takeaways

The National Institute of Standards and Technology will stop assigning severity scores to lower-priority vulnerabilities due to the growing workload from rising submission volumes.

Starting April 15, the service will only analyze and provide additional details (e.g., severity rating, product lists) for security issues that meet specific criteria related to the risk they pose.

The National Vulnerability Database (NVD) will still list all submitted vulnerabilities, but those considered low priority will have a severity rating only from the CVE Numbering Authority (CNA) that evaluated and submitted it.

In an announcement this week, the non-regulatory federal agency said it will only provide additional details for vulnerabilities that meet one of the following criteria:

are in CISA’s Known Exploited Vulnerabilities (KEV) catalog

affect the U.S. federal government software

involve critical software as per Executive Order 14028

NIST explained that the decision was driven by the large number of submissions, which grew by 263% recently and continued to accelerate in 2026. The organization enriched 42,000 CVEs in 2025, but it can no longer keep up with the increasing volume.

NIST NVD is a public, centralized database of known software and hardware vulnerabilities, which also provides additional descriptions and analyses on top of the unique identifiers (CVE IDs) assigned by CNAs, such as vendors and the not-for-profit The MITRE Corporation.

The point of enriching vulnerability details is to make CVE entries usable for risk management, including assigning severity scores, identifying affected product versions, classifying weaknesses, and providing links to advisories, patches, or related research.

... continue reading