Cybersecurity Crisis: CVE Program’s Future Uncertain as DHS Drops Contract

By Dan Evert, CCNP   Published: 04/16/25   Updated: 10/22/26   3 min read

Cybersecurity Crisis: CVE Program’s Future Uncertain as DHS Drops Contract

At a glance:

Why the CVE program matters

The Common Vulnerabilities and Exposures (CVE) program is the shared system for naming and cataloging security flaws in software and hardware. Each flaw gets a unique ID. Defenders, vendors and researchers everywhere use those IDs to talk about the same problem, share information and prioritize fixes. Since it began in 1999, it has become a backbone of how the industry handles vulnerabilities.

In April 2025, that system suddenly looked fragile. MITRE, which runs the program under a contract funded by the Department of Homeland Security, warned in a letter from vice president Yosry Barsoum that the contract would expire on April 16, 2025. The news set off alarm across the security community.

What a lapse would have meant

Without a renewed contract, the program’s core work could have stalled. New CVE IDs might not have been assigned, and records might have stopped updating, leaving defenders around the world working from incomplete information at exactly the moment new flaws were being disclosed.

Security professionals warned that losing fast, accurate vulnerability tracking would make threats harder to manage and damage the cooperation the field depends on.

The global stakes

The impact would have reached far beyond the United States. Organizations everywhere rely on timely CVE data to decide what to patch. A gap helps attackers.

Many in the field describe the CVE system as a common language for security problems. Without it, international efforts risk splintering.

A last-minute extension

At the last minute, CISA executed an option period on the contract, extending MITRE’s funding for 11 months and avoiding a lapse in service. The relief was real but temporary, and calls for a more stable model began immediately.

Some proposed new funding sources and more international involvement to keep the program going. A group of CVE board members also announced a new nonprofit, the CVE Foundation, aimed at securing the program’s independence.

What the scare revealed

The episode showed how fragile some core security infrastructure is. Governments and industry need to agree on how such shared services are run and paid for.

It also raised questions about other essential security programs that depend on a single government contract.

Fixing the funding for good

The CVE scare was a reminder of how interconnected security systems are. Securing the program is not only a job for DHS or the U.S. government. The whole security community has a stake in it.

The near-lapse is a chance to rethink how essential services like the CVE program are managed and funded before the extension runs out.

Durable funding, clear governance and broad support will matter more than any single contract renewal.

Stay Current

Newer CyberExperts coverage on this topic

This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.

Latest Daily Brief

Friday’s brief: GitLab’s 10.0 fix, then VeloCloud attacks, a poisoned LiteLLM release and PHP2Shell logs to check

The fastest way to catch up on what changed after this article was published.

Read Today's Brief

Dan Evert, CCNP

Dan Evert is a self proclaimed Router Jockey. Dan got heavily involved in networking right out of high school and has never looked back! Dan is giving back by working with high school students to get them involved and interested in Networking and Security.