NVD Backlog, are we there yet? has CISA, and the Vulnrichment Program created a dent?

NVD Burndown

The NVD vulnerability backlog reached 16,476 vulnerabilities in July despite the enrichment and the attempt to burn down the backlog, which, by now, should be at 9,973 vulnerabilities; we will explore in this article some of the progress and how Phoenix Security ASPM is addressing them. This backlog is significantly higher than the 9,973 vulnerabilities forecasted to meet the 2025 end-of-year analysis goal. As vendors and institutions, we are concerned that the backlog and data quality will get worse with initiatives like Linux announcing every bug as a vulnerability, spiking to 5103 new just in May against the 3034 average new monthly vulnerabilities.

Phoenix Security UVM and ASPM modules have already started pre-processing several vulnerabilities, ingesting enrichment CISA and other raw sources like CVE.org, and processing with AI-based enrichment for CWE, CVE, Technical impact and Category of the issues. Managing installed software and software vulnerabilities is a critical aspect of cybersecurity. Organisations rely on comprehensive databases and enrichment programs to stay ahead of potential threats. The National Vulnerability Database (NVD) and the Cybersecurity and Infrastructure Security Agency (CISA) are two key players in this field. Recently, CISA launched the Vulnrichment program to address the growing backlog of vulnerabilities, which could reshape how we manage and mitigate cyber threats.

This article provides an in-depth look at the NVD, the impact on UVM and ASPM, the role of CISA, the vulnerability backlog, and how the Vulnrichment program aims to tackle the backlog burndown and current challenges in vulnerability management.

What is the National Vulnerability Database (NVD) and Vulnerability Backlog?

The NVD is the U.S. government’s repository of standards-based vulnerability management data, managed by the National Institute of Standards and Technology (NIST). It includes databases of security checklists, security-related software flaws, misconfigurations, product names, and impact metrics. Key features include:

  • Common Vulnerabilities and Exposures (CVE): A list of publicly disclosed information security vulnerabilities and exposures.
  • Common Platform Enumeration (CPE): A standardized method for describing and identifying classes of applications, operating systems, and hardware devices.
  • Common Vulnerability Scoring System (CVSS): An industry standard for assessing the severity of computer system security vulnerabilities.
  • Common Weakness Enumeration (CWE): A list of software weaknesses.

The NVD plays a crucial role in centralizing vulnerability information, but recent challenges have led to a significant backlog in vulnerability analysis and enrichment.

What is CISA Vulnrichment?

The Cybersecurity and Infrastructure Security Agency (CISA) is a federal agency under the Department of Homeland Security (DHS). It is responsible for enhancing the security, resilience, and reliability of the nation’s cybersecurity and communications infrastructure.

CISA’s Key Responsibilities:

  • Cybersecurity: Protecting federal networks and collaborating with private sector partners to defend critical infrastructure.
  • Infrastructure Security: Ensuring the security of the physical infrastructure and assets that are essential to the nation’s security, economy, and public health.
  • Emergency Communications: Improving emergency communications capabilities across the nation.

CISA is often the first to issue public warnings about vulnerabilities actively exploited in the wild. This proactive approach helps organizations take immediate action to protect their systems.

Reasons for the NVD Vulnerability Backlog

Phoenix Security ASPM
Phoenix Security UVM
NVD Backlog
CISA
Vulnerabilities

Several factors have contributed to the current backlog in the NVD:

Resource Constraints

One of the primary reasons for the backlog is the limited resources and budget constraints faced by NIST. With insufficient funding and staffing, the agency struggled to keep up with the volume of new vulnerabilities being reported. This has led to delays in analyzing and enriching CVE records, resulting in a significant accumulation of unprocessed data.

Speculation on New CPE Initiative

The introduction of a new CPE initiative has also been speculated to contribute to the backlog. Implementing a new system for describing and identifying software and hardware products requires time and effort. While ultimately beneficial for standardization and accuracy, this change has temporarily slowed down the enrichment process.

Change in CVE Format

Another factor is the adoption of the new CVE format (version 5.1). While the updated format aims to provide more detailed and structured information, the transition has required adjustments in processes and tools used for vulnerability analysis. This transition period has contributed to delays in processing and enriching CVE records.

Current State of the Vulnerability Backlog

As of July, the NVD faces a significant backlog in vulnerability analysis. Here are some critical statistics:

MonthForecasted BacklogActual Backlog
January2000
February1000
March21522152
April7377.53945
May126038274
June1153912603
July997316476
Phoenix Security ASPM
Phoenix Security UVM
NVD Backlog
CISA
Vulnerabilities

As of July 14, 2024, the NVD faces a significant backlog in vulnerability analysis. According to the Automation Working Group’s report on May 22, CISA is currently analyzing and enriching approximately 200 vulnerabilities per day. Nonetheless the exploding size of the backlog is dwarfing the initiative

For additional statistics on vulnerability Phoenix Security UVM Phoenix Security ASPM and exploitability, refer to:

Given these numbers, the new team will take approximately 10-11 months to clear the current backlog, assuming there are no disruptions. This sets the first target date for a clear backlog around March 2025, nonetheless at the current pace, this is unlikely unless the vulnerability number diverges (unlikely given the 5103 in May)

For a more comprehensive analysis of the other implications of NVD backlog, refer to nvd-exploited vulnerabilities article and vulncheck report 

Get in touch for a maturity assessment

Feasibility and Timeline

The CISA team’s analysis and enrichment capacity is projected at 4,364 vulnerabilities per month. Considering the conservative estimate of 2,981 new vulnerabilities discovered each month, the team aims to reduce the backlog to zero by March 2025, although this looks unavailable.

Conclusion

The NVD, CISA, and the Enrichment program are critical components of the United States cybersecurity infrastructure. The recent backlog in vulnerability analysis highlights the urgent need for enhanced data enrichment processes and collaboration among all stakeholders. By addressing these challenges, the Vulnrichment program aims to provide organizations with the timely and accurate information they need to secure their systems against evolving cyber threats.

With no mandate but a hopeful target of March 2025 for resolving the current backlog, the cybersecurity community must remain vigilant and proactive in implementing effective vulnerability management strategies. This will not only improve organisational security but also contribute to the overall resilience of the nation’s critical infrastructure.

How can Phoenix Security ASPM and UVM help in addressing the NVD Vulnerability Backlog

In response to the challenges faced by the NVD, Phoenix Security UVM and ASPM modules offer comprehensive Vulnerability management, ASPM and Vulnerability threat Intelligence solutions that automate the enrichment process by synchronizing with NVD, CVE.org, augmenting and extracting meaning for technical analysis and syncing with the Vulnrichment initiative. At Phoenix, we also started to enrich vulnerabilities with AI-derived CWE, Technical Impact, and Capec to compensate for the shortcomings of the NVD database. Phoenix Security connects to over 32 vulnerability intelligence sources and ensures comprehensive and timely enrichment of CVE data. Their innovative 4D contextual risk-based formula also provides enhanced training and prioritization, enabling organizations to manage and mitigate vulnerabilities effectively. This advanced approach not only streamlines the enrichment process but also empowers security teams with the tools and insights needed to stay ahead of evolving threats.

Get in touch for a maturity assessment

Francesco is an internationally renowned public speaker, with multiple interviews in high-profile publications (eg. Forbes), and an author of numerous books and articles, who utilises his platform to evangelize the importance of Cloud security and cutting-edge technologies on a global scale.

Discuss this blog with our community on Slack

Join our AppSec Phoenix community on Slack to discuss this blog and other news with our professional security team

From our Blog

The journey of securing an organization’s application landscape varies dramatically, depending on where a company stands in its maturity. Early-stage startups with small security teams face challenges not only with vulnerabilities but also with scaling their security processes in line with their growth. On the flip side, established enterprises struggle with managing complex environments, prioritizing remediation, and dealing with vast amounts of vulnerabilities while staying ahead of sophisticated threats. For startups, the focus is clear—establish visibility and ensure core security practices are in place. Application Security Posture Management (ASPM) tools provide a straightforward, automated approach to detecting vulnerabilities and enforcing policies. These solutions help reduce risk quickly without overburdening small security teams. Mature organizations, on the other hand, are tackling a different set of problems. With the sheer number of vulnerabilities and an increasingly complicated threat landscape, enterprises need to fine-tune their approach. The goal shifts toward intelligent remediation, leveraging real-time threat intelligence and advanced risk prioritization. ASPM tools at this stage do more than just detect vulnerabilities—they provide context, enable proactive decision-making, and streamline the entire remediation process. The emergence of AI-assisted code generation has further complicated security in both environments. These tools, while speeding up development, are often responsible for introducing new vulnerabilities into applications at a faster pace than traditional methods. The challenge is clear: AI-generated code can hide flaws that are difficult to catch in the rush of innovation. Both startups and enterprises need to adjust their security posture to account for these new risks. ASPM platforms, like Phoenix Security, provide automated scanning of code before it hits production, ensuring that flaws don’t make it past the first line of defense. Meanwhile, organizations are also grappling with the backlog crisis in the National Vulnerability Database (NVD). A staggering number of CVEs remain unprocessed, leaving many businesses with limited data on which to base their patching decisions. While these delays leave companies vulnerable, Phoenix Security steps in by cross-referencing CVE data with known exploits and live threat intelligence, helping organizations stay ahead despite the lag in official vulnerability reporting. Whether just starting their security program or managing a complex infrastructure, organizations need a toolset that adapts with them. Phoenix Security enables businesses of any size to prioritize vulnerabilities based on actual risk, not just theoretical impact, helping security teams navigate the evolving threat landscape with speed and accuracy.
Francesco Cipollone
The cybersecurity world is reeling as MITRE’s funding for the CVE and NVD systems expires, disrupting the backbone of global vulnerability management. As traditional sources like the National Vulnerability Database collapse under funding cuts and submission backlogs, security teams face delays, incomplete data, and loss of automation in remediation pipelines. This isn’t just a data problem—it’s a structural crisis for application security and vulnerability correlation. In this landscape of uncertainty, Phoenix Security’s ASPM platform steps up with a code-to-cloud correlation engine that doesn’t depend on outdated data workflows. By connecting code-level insights (including tools like Semgrep) to runtime and cloud environments, Phoenix enables faster, context-aware vulnerability remediation—even as NVD and CVE pipelines deteriorate. This article dives into the implications of the CVE shutdown and how Phoenix Security is helping security and development teams transition to a resilient, correlation-first approach to cybersecurity.
Francesco Cipollone
Learn how to predict ransomware risks and vulnerability exploitation using a threat-centric approach. Explore data-driven insights, verified exploit trends, and methods for assessing the likelihood of attacks with key references to CISA KEV, EPSS, and Phoenix Security’s 4D Risk Formula.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
Remote Code Execution flaws continue to undermine Kubernetes ingress integrity. IngressNightmare (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) showcases severe threat vectors in NGINX-based proxies, leading to cluster-wide exposure. ASPM, robust remediation tactics, and strong application security solutions—like Phoenix Security—mitigate these vulnerabilities before ransomware groups exploit them.
Francesco Cipollone
The recent Google acquisition of Wiz for $32 billion has sent shockwaves through the cybersecurity industry, particularly in the realm of Application Security Posture Management (ASPM). This monumental deal highlights the critical importance of cloud security and the growing demand for robust ASPM solutions. While the acquisition promises potential benefits for Google Cloud users, it also raises concerns about vendor lock-in and the future of cloud-agnostic security. Explore the implications of this acquisition and discover how neutral ASPM solutions like Phoenix Security can bridge the gap in multi-cloud environments, ensuring continuous, collaborative, and comprehensive security from code to cloud.” – Find Assets/Vulns by Scanner – Detailed findings Location information Risk-based Posture Management – Risk and Risk Magnitude for Assets – Filter assets and vulnerabilities by source scanner Integrations – BurpSuite XML Import – Assessment Import API Other Improvements – Improved multi-selection in filters – New CVSS Score column in Vulnerabilities
Alfonso Eusebio
Derek

Derek Fisher

Head of product security at a global fintech

Derek Fisher – Head of product security at a global fintech. Speaker, instructor, and author in application security.

Derek is an award winning author of a children’s book series in cybersecurity as well as the author of “The Application Security Handbook.” He is a university instructor at Temple University where he teaches software development security to undergraduate and graduate students. He is a speaker on topics in the cybersecurity space and has led teams, large and small, at organizations in the healthcare and financial industries. He has built and matured information security teams as well as implemented organizational information security strategies to reduce the organizations risk.

Derek got his start in the hardware engineering space where he learned about designing circuits and building assemblies for commercial and military applications. He later pursued a computer science degree in order to advance a career in software development. This is where Derek was introduced to cybersecurity and soon caught the bug. He found a mentor to help him grow in cybersecurity and then pursued a graduate degree in the subject.

Since then Derek has worked in the product security space as an architect and leader. He has led teams to deliver more secure software in organizations from multiple industries. His focus has been to raise the security awareness of the engineering organization while maintaining a practice of secure code development, delivery, and operations.

In his role, Jeevan handles a range of tasks, from architecting security solutions to collaborating with Engineering Leadership to address security vulnerabilities at scale and embed security into the fabric of the organization.

Jeevan Singh

Jeevan Singh

Founder of Manicode Security

Jeevan Singh is the Director of Security Engineering at Rippling, with a background spanning various Engineering and Security leadership roles over the course of his career. He’s dedicated to the integration of security practices into software development, working to create a security-aware culture within organizations and imparting security best practices to the team.
In his role, Jeevan handles a range of tasks, from architecting security solutions to collaborating with Engineering Leadership to address security vulnerabilities at scale and embed security into the fabric of the organization.

James

James Berthoty

Founder of Latio Tech

James Berthoty has over ten years of experience across product and security domains. He founded Latio Tech to help companies find the right security tools for their needs without vendor bias.

christophe

Christophe Parisel

Senior Cloud Security Architect

Senior Cloud Security Architect

Chris

Chris Romeo

Co-Founder
Security Journey

Chris Romeo is a leading voice and thinker in application security, threat modeling, and security champions and the CEO of Devici and General Partner at Kerr Ventures. Chris hosts the award-winning “Application Security Podcast,” “The Security Table,” and “The Threat Modeling Podcast” and is a highly rated industry speaker and trainer, featured at the RSA Conference, the AppSec Village @ DefCon, OWASP Global AppSec, ISC2 Security Congress, InfoSec World and All Day DevOps. Chris founded Security Journey, a security education company, leading to an exit in 2022. Chris was the Chief Security Advocate at Cisco, spreading security knowledge through education and champion programs. Chris has twenty-six years of security experience, holding positions across the gamut, including application security, security engineering, incident response, and various Executive roles. Chris holds the CISSP and CSSLP certifications.

jim

Jim Manico

Founder of Manicode Security

Jim Manico is the founder of Manicode Security, where he trains software developers on secure coding and security engineering. Jim is also the founder of Brakeman Security, Inc. and an investor/advisor for Signal Sciences. He is the author of Iron-Clad Java: Building Secure Web Applications (McGraw-Hill), a frequent speaker on secure software practices, and a member of the JavaOne Rockstar speaker community. Jim is also a volunteer for and former board member of the OWASP foundation.

Join our Mailing list!

Get all the latest news, exclusive deals, and feature updates.

The IKIGAI concept
x  Powerful Protection for WordPress, from Shield Security
This Site Is Protected By
ShieldPRO