Government’s Near Miss: The Cybersecurity Database That Almost Vanished
Summary
- The CVE program, the system used worldwide to track software vulnerabilities, nearly lost its federal funding in April 2025.
- MITRE’s contract to run the program was due to expire on April 16, 2025.
- CISA extended the contract at the last minute after a public outcry from the security community.
- The scare raised questions about how the program is funded and governed.
A last-minute rescue
This week the security world got a scare. On April 15, 2025, MITRE warned that its government contract to run the Common Vulnerabilities and Exposures (CVE) program would expire the next day. The CVE program assigns the standard IDs used to track software vulnerabilities around the world. Losing it would have disrupted vulnerability tracking almost everywhere.
Why CVE matters
CVE is the shared catalog of publicly known vulnerabilities. Funded through the Cybersecurity and Infrastructure Security Agency (CISA) and run by MITRE, it gives each flaw a unique ID that vendors, researchers and defenders all use.
Security scanners, patch tools, advisories and national vulnerability databases all rely on those IDs. Without them, coordinating fixes would get much harder, and defenders would struggle to know which bugs they’re talking about.
Start your morning with the signal that matters.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
What went wrong
An earlier version of this article described the near-miss as a budgeting oversight caught during final budget reconciliation. That was not accurate. The issue was the scheduled expiration of MITRE’s contract, at a time when federal agencies were cutting spending. MITRE’s warning letter set off alarm across the industry.
An anonymous quote attributed to a senior CISA official in an earlier version could not be verified and has been removed. CISA said late on April 15 that it had executed the option period on the contract so there would be no lapse in CVE services.
How the industry reacted
The security community reacted quickly. Members of the CVE board launched a separate nonprofit, the CVE Foundation, to work toward independent governance. Vendors and researchers publicly pressed for a long-term fix.
The extension bought about 11 months. It didn’t settle the program’s long-term funding or governance.
What it means for the future
The episode showed how much of the world’s security tooling depends on one program with a single government funder. A short contract gap could have caused confusion for vendors and defenders everywhere.
Start your morning with the signal that matters.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Some in the industry want CVE moved to a more independent structure with multiple funders, so it isn’t exposed to one agency’s budget decisions.
Lessons from the CVE scare
The close call is a reminder that basic security infrastructure can be fragile. Policymakers, vendors and researchers need a stable way to fund it.
The CVE program survived this time. The next contract deadline is the one to watch.
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.
Citrix NetScaler CVE-2026-19490: The Auth Bypass That Went From PoC to Probes in a Day
CVE-2026-19490 is a CVSS 9.3 NetScaler Gateway/AAA auth bypass. A public PoC on Sept 2 was followed by live probes within a...
PaperCut NG/MF: The Print Server That Learned Remote Code Execution Again
CVE-2026-81578 and CVE-2026-82078 chain to pre-auth RCE on PaperCut Application Server. Confirm Emergency Patch Release 2, restrict admin exposure, and hunt like...
JFrog Artifactory CVE-2026-82329: Empty Join Key, Full Admin Token, Busy Scanners
CVE-2026-82329 lets attackers forge Artifactory admin tokens via a deterministic empty join key. Mass scanning peaked near 406,000 attempts; patch fixed builds...
Friday’s brief: Apache’s HTTP/2 fix, then Check Point break-ins, a ScreenConnect add-on and a GitHub secret stealer
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.