
Many security personnel face numbers like 'CVE-2025-XXXX' daily.
This is a unique number assigned by the CVE (Common Vulnerabilities and Exposures) system, which organizes global security threat information.
CVE, literally, is a list of 'weaknesses' in software that hackers around the world might target.
However, the CVE system has been showing signs of instability recently.
CVE system instability
The confusion in the CVE system was due to the lack of funding at MITRE, which operates the system.
MITRE, a U.S. nonprofit organization, runs the CVE system with funding from the U.S. Cybersecurity and Infrastructure Security Agency (CISA). However, this funding was at risk of being cut off by the end of April 2025 but was barely revived.
Fortunately, CISA allocated funding for MITRE to continue operating the CVE system for another 11 months. The problem is the uncertainty about what will happen once this period ends.
The CVE system is essential infrastructure relied upon by numerous security companies and government agencies. Yet, it operates on a survival structure based on yearly funding.
If U.S. government funding stops, vulnerability registration could be delayed or halted. In other words, security response timing could be delayed.
The CVE system is U.S.-centric. In other words, the standard for global cybersecurity is effectively dictated by the 'U.S. government.'
If U.S. policies change or the administration changes, the global security response system could be disrupted as well.
Therefore, there is a growing call to change the structure that relies on a single country.
Additionally, there are opinions that the latest technologies are not suited for the CVE framework.
CVE fundamentally targets clear defects (bugs) in software or hardware. However, in the current era of widespread cloud, the situation is complex.
Cloud services are updated daily and change automatically without user intervention. Some services pose security risks even if the user 'does nothing.' Such issues often don't get registered in CVE. CVE typically requires 'patch target' or 'update target' to be clear, but this structure doesn't fit the cloud.
While CVE suits traditional software models, blind spots occur in technology-based environments like cloud, SaaS, AI, and API-integrated services.
How does the security community respond?
For this reason, the security community is currently considering 'alternatives or supplements to CVE.' New systems are being created to address vulnerabilities by entities such as Europe (EUVD), China (CNNVD), and private companies.
Europe (EU) EUVD
“We will not be entirely dependent on a U.S.-centric system. Europe will assess with European perspectives.”
ENISA, the European Union's cybersecurity agency, launched the EUVD (European Vulnerability Database). ENISA announced that EUVD, which was in beta, would be officially launched on May 13, 2025. This action came amidst ongoing controversy over CVE due to U.S. CISA budget cuts.
ENISA introduced its system as the existing CVE system struggled to reflect European policies and realities.
EUVD has a unique identification system similar to CVE (e.g., EUVD-2025-1234), ensuring interoperability and compatibility by listing CVE numbers as well.
EUVD is organized around the cooperation results of CSIRT between countries or actual exploitation cases, making it easy to prioritize risks. It's designed to automatically integrate with open-source analysis tools like Vulnerability-Lookup.
China CNNVD
“Cybersecurity should also be locally oriented. Information sovereignty is the start of security.”
The Chinese government operates the official vulnerability database CNNVD (China National Vulnerability Database).
CNNVD is run by CNITSEC (China Information Technology Security Evaluation Center) under the Ministry of State Security (MSS). CNITSEC, part of the 13th bureau of MSS, handles China's cyber operations and intelligence gathering.
Officially, CNNVD analyzes security vulnerabilities in information technology products and systems. It assesses the security risks of the party's and government's information networks and critical information systems, and conducts security tests and evaluations, similar to South Korea's NIS.
CNNVD has its numbering and registration system while referencing U.S. CVE.
Vulnerabilities in Chinese company products are often registered with CNNVD before CVE. Despite censorship control controversies, CNNVD has become an essential system for security responses within China. Some vulnerabilities are registered more quickly than with CVE, leading international researchers to also refer to CNNVD.
CNNVD operates as part of China's cybersecurity strategy and information gathering activities. It's known to function beyond a simple vulnerability database. The international community has raised questions about its reliability due to issues like lack of transparency and publication delays.
Security experts use CNNVD information with cross-verification against various vulnerability databases to ensure accuracy and reliability.
Private Companies as Businesses
Private companies are overcoming the limitations of the existing CVE system by providing faster and more detailed security information as a business. Private vulnerability DBs focus on vulnerabilities not registered with CVE or latest security threat information.
Cybersecurity company Flashpoint operates VulnDB. Originally created by Risk Based Security, it is now managed by Flashpoint.
It is a commercial vulnerability DB targeting corporate clients. It's faster and provides more information than CVE. VulnDB includes unofficial vulnerability information not found in CVE, featuring specific details like exploit codes (PoC), real damage examples, and countermeasures. Companies can connect VulnDB via API to integrate it into automated security systems.
Snyk operates a database providing vulnerability information for open-source and cloud environments. This database includes vulnerabilities for various package managers and cloud platforms like npm, Maven, and pip, allowing developers to identify and address potential security issues in the libraries and dependencies they use.
What's the strategy for corporate security officers?
Let's Look at Various Vulnerability Databases Alongside CVE
Many security teams manage vulnerabilities based solely on CVE. However, we are now in an era where we must look at diverse databases, like those from Europe, China, and private companies.
For example, VulnDB holds over 100,000 vulnerabilities that are not registered in CVE. This means there are quite a few security threats you could miss by only looking at CVE.
Don't Wait for 'Official Registration,' Find Them First
The biggest limitation of CVE is the speed of 'official registration.' Even China's CNNVD has delayed or manipulated release dates intentionally in the past. Now, security personnel should not wait for CVE but instead identify vulnerabilities first in collaboration with offensive security experts.
Choose the Database That Suits Our Company's Environment
Having many databases doesn't mean you can use them all. You should choose and use a database that suits our company's system and network configuration.
For example, if you focus on open-source packages, Snyk is useful, and if covering entire IT assets, VulnDB is beneficial. Choosing data sources according to our environment and prioritizing is efficient.
CVE is still a useful standard, but it's an era where relying on it alone is insufficient. Now, an active security operation strategy is needed that references diverse vulnerability databases, compares information, and applies it to our organization.
Change is ongoing. Security officers in companies should gather information, build structures, and enhance responsiveness in this trend.
Popular Articles