Close today

Go to Top

Go to Top

The Major Shift in Security Vulnerability Management
The Major Shift in Security Vulnerability Management

Security Insights

Security Insights

Security Insights

The Major Shift in Security Vulnerability Management

The Major Shift in Security Vulnerability Management

The Major Shift in Security Vulnerability Management

In-soon Kim

In-soon Kim

Content

Content

Content

Security vulnerabilities use a numbering system called CVE (Common Vulnerabilities and Exposures). The CVE number itself is an identifier that distinguishes vulnerabilities. For example, a number like 'CVE-2026-12345' refers to the exact same vulnerability anywhere in the world.

Launched in 1999, CVE assigns unique numbers to publicly known security vulnerabilities. Security firms, software developers, and government agencies use these numbers to share vulnerability info and manage patches. 

However, CVE numbers alone do not help companies decide what to fix first. They also need to know how dangerous a vulnerability is, which products and versions are affected, and what type of flaw it is.

The National Institute of Standards and Technology (NIST) has been enriching this data. NIST added risk levels and product info to CVEs via the National Vulnerability Database (NVD). Many security tools and vulnerability management systems globally use this data to prioritize actions.



NIST Overhauls NVD Operations

However, this structure is changing. The US NIST announced it will reorganize NVD operations on April 15, 2026. As analyzing all CVEs the same way became difficult, they decided to prioritize and enrich key vulnerabilities first.
This is another shift following budget cuts, contract expirations, and extension disputes in April 2025 at MITRE, the non-profit running the CVE Program, and CISA. 

NIST's priority for analysis targets CVEs in CISA's 'Known Exploited Vulnerabilities Catalog (KEV)'. This includes CVEs in software used by the US federal government, and key software CVEs defined by US Executive Order EO 14028. 

Here, 'key software' does not just mean software for critical infrastructure like power plants or factories. It is a concept separately defining software that performs functions critical to US federal operations and security.

CVEs not included in the priorities are still registered in the NVD. However, they may be classified as 'Lowest Priority—Not Scheduled for Immediate Enrichment'. The name of the vulnerability goes on the list, but NIST's detailed analysis may be delayed. 

Currently, CVEs contain more than just numbers. The CVE Numbering Authority (CNA), which issues CVE numbers, provides vulnerability descriptions, affected products, flaw types, and risk scores. 

The issue is that analysis capabilities and the scope of information provided vary by CNA. Some CVEs have detailed product info and risk scores, while others may only have a brief description and reference links.

The NIST NVD has played a role in narrowing this gap. NIST enriched CVSS, CPE, and CWE. CVSS shows "how severe it is." CPE tells "which products are affected." CWE explains "what kind of flaw it is."

  • CVSS: Technical severity of the vulnerability itself

  • CPE: System to standardize and display affected products and versions

  • CWE: Classification identifying what type of software/hardware flaw it is

Combining this information makes it easier for vulnerability scanners and management tools to automatically determine if "our company's product has an issue" or "this vulnerability must be fixed first."



From general checkup to ER style

The approach chosen by the NVD is close to the 'Emergency Room Triage' system.

Triage is a system used in ERs or disaster scenes to prioritize patient treatment. When patients flood in at once, medical staff cannot treat them in order of arrival. They treat the critical first and delay the less urgent.

The shift at the NVD is similar. While they once tried to analyze all possible CVEs to append standardized data, they now prioritize vulnerabilities used in actual attacks or that greatly affect the US government.

This change is not because NIST is trying to cut back on work. NIST enriched about 42,000 CVEs in 2025. This throughput is 45% higher than the previous record. Yet, they cannot keep pace with newly registered vulnerabilities. CVE submissions grew by 263% from 2020 to 2025. Q1 2026 submissions are also a third higher than the same period last year. Even with faster analysis, they face a surge in vulnerabilities. 

By adopting the new model, NIST moved unanalyzed CVEs published before March 1, 2026, to 'Not Scheduled' status. According to industry analysis, about 29,000 CVEs were reclassified. They did not finish analyzing these 29,000 cases; they merely shifted them from the queue to 'Not Scheduled' status.

NIST explained they might analyze past vulnerabilities if resources allow. They also set up a process for users to request analysis of specific CVEs via email.

However, this is a backup measure to focus limited resources on critical vulnerabilities. It is not a bulk processing method that can replace the legacy structure of analyzing tens of thousands of vulnerabilities. 



The exact meaning of 'no score'

Exclusion from NVD's priority analysis does not mean all information disappears. If a CNA has already provided CVSS, CWE, or affected product information, that information may remain in the CVE record. The difference is that it is now difficult to expect NIST to provide separate analysis information for every CVE.

NIST has decided not to routinely re-score CVEs if a CNA has already provided a CVSS score. This measure is intended to reduce redundancy and focus limited staff on high-priority vulnerabilities.

The issue is that CNAs have different analysis capabilities and standards. While some records detail products and versions, others may lack information. There is also a possibility that different organizations will score the same vulnerability differently.

Going forward, one should not assume a vulnerability is not dangerous simply because there is 'no official score.' A lack of a score does not mean safe; it may mean sufficient analysis has not yet been conducted.

To avoid relying solely on US information, Europe is expanding its own databases and decentralized identification systems.

Much of the responsibility for assessing security vulnerabilities is now shifting from national agencies and public databases to individual organizations.



Change vulnerability management rules

Summing up the quarterly counts of the CVE program, new CVEs in 2025 reached an all-time high of about 48,000. In Q4 2025 alone, 12,796 CVE records were published. The upward trend is continuing into 2026. 

What is clear is that the discovery, disclosure, and exploitation of vulnerabilities are all accelerating. Analyzing all vulnerabilities with the same depth and patching them at the same speed is no longer a realistic solution.

Going forward, organizations must not prioritize actions solely based on CVSS scores. At a minimum, the following factors must be examined together.

  • Is it a product that our organization actually uses?

  • Is it exposed to the Internet or a partner's network?

  • Is it connected to critical data and core operations?

  • Is it being actively exploited in real-world attacks?

  • Has the exploit code been publicly released?

  • Are accounts or cloud privileges excessively configured?

  • Can it be chained with other vulnerabilities to create an attack path?

  • Can security controls or detection systems block the attack?

The standard for vulnerability management must shift from "the highest score in the world" to "the most dangerous attack path for our organization." To achieve this, organizations must utilize not only NVD, but also vendor security advisories, CISA KEV, EPSS (Exploit Prediction Scoring System), EUVD (European Vulnerability Database), commercial threat intelligence, SBOM (Software Bill of Materials), asset management data, and external exposure information.

It is critical to verify how vulnerabilities connect to actual assets and how far an attacker can move laterally.

"Even without an external scorecard, can we determine which vulnerability is truly dangerous in our system?"

Organizations that cannot answer this question face two major risks.

One is the vulnerability that was missed because there was no score. The other is the vulnerability that was postponed due to a low score, but became a critical attack path when chained with other weaknesses.

The era of being attacked due to a lack of information is passing. Now, we are entering an era where too much information causes us to miss the truly critical risks.

The core of vulnerability management is not about receiving more lists. It is the ability to determine what is truly dangerous based on our organization's assets, operations, privileges, and network.



References


  1. NIST, NVD Operation Reorganization Announcement
    April 15, 2026 reorganization, priority analysis criteria, 263% increase, approx. 42k processed in 2025, CNA score utilization policy.

  2. NVD Official Website
    Explanation of NVD's role and SCAP-based vulnerability management information.

  3. NVD Status Dashboard
    Current processing status such as Awaiting Enrichment, Undergoing Enrichment, Not Scheduled, etc.

  4. CISA, Official Position on CVE Program Contract
    CISA's explanation that it was a contract administration issue, not a funding issue.

  5. Nextgov, CISA's MITRE CVE Contract Extension Report
    Execution process of the 11-month extension option just before the contract expired.

  6. ENISA, Official EUVD Announcement
    EUVD's NIS2 basis, data composition, CVE·KEV·vendor information linkage method.

  7. Official EUVD Database
    European Union vulnerability information search service.

  8. GCVE, db.gcve.eu Public Announcement
    Integration database release on Jan 7, 2026, and connection with 25+ information sources.

  9. GCVE Official News & Tech Resources
    GCVE's decentralized vulnerability identification/issuance structure & project evolution.

  10. db.gcve.eu Official Database
    Integrated search service for GCVE and existing vulnerability information sources.

  11. CVE Program 2025 Q4 Report
    Issuance statistics including 12,796 CVE records in Q4 2025.

  12. FIRST, Official CVSS Guide
    CVSS purpose and technical severity assessment criteria.

  13. NVD, Official CPE Guide
    CPE system that standardizes and identifies products and versions.

  14. MITRE, Official CWE Website
    Classification system for software and hardware weakness types.

In-soon Kim

In-soon Kim

Start-up College Adjunct Professor at Gachon University
Start-up College Adjunct Professor at Gachon University

Former desk member of the Electronic Newspaper ICT Convergence Department, active as a cyber security journalist and communication expert for 20 years.

Former desk member of the Electronic Newspaper ICT Convergence Department, active as a cyber security journalist and communication expert for 20 years.

The Beginning of Flawless Security System, From the Expertise of the No.1 White Hacker

Prepare Before a Security Incident Occurs

The Beginning of Flawless Security System, From the Expertise of the No.1 White Hacker

Prepare Before a Security Incident Occurs

The Beginning of Flawless Security System, From the Expertise of the No.1 White Hacker

Prepare Before a Security Incident Occurs

Subscribe

Find this content useful?
Subscribe to the Enki Letter!

Copyright © 2025. ENKI WhiteHat Co., Ltd. All rights reserved.

Copyright © 2025. ENKI WhiteHat Co., Ltd. All rights reserved.

Copyright © 2025. ENKI WhiteHat Co., Ltd. All rights reserved.