When a security update fixes "CVE-2025-53770", that label comes from one shared system: the Common Vulnerabilities and Exposures (CVE) programme. It gives every publicly known software flaw a unique name so that vendors, security tools and defenders all talk about the same thing. In April 2025, that system came within hours of losing its funding.
What happened
On 15 April 2025, Yosry Barsoum, a vice-president at MITRE — the US non-profit that runs CVE on behalf of the government — wrote to the CVE Board that its contract to operate CVE and related programmes was due to expire the next day, Wednesday 16 April.
He warned that a break in service would have "multiple impacts to CVE, including deterioration of national vulnerability databases and advisories, tool vendors, incident response operations, and all manner of critical infrastructure" (BleepingComputer).
A CISA spokesperson initially confirmed that the contract would lapse. Then, late on 15 April, CISA executed an option period "to ensure there will be no lapse in critical CVE services", adding that "The CVE Program is invaluable to the cyber community and a priority of CISA" (The Record). The extension ran for 11 months, to March 2026.
The response: independence and alternatives
The scare prompted action on two fronts:
- A CVE Foundation. Members of the CVE Board announced a new foundation to "ensure the long-term viability, stability, and independence" of the programme. As board member Kent Landfield put it, CVE is "too important to be vulnerable itself" (The Record).
- Europe's own database. On 13 May 2025, the EU's cyber security agency ENISA made its European Vulnerability Database (EUVD) operational, as required by the NIS2 Directive. It offers dashboards for critical vulnerabilities, actively exploited vulnerabilities and vulnerabilities coordinated by European CSIRTs, and draws on CVE data and CISA's Known Exploited Vulnerabilities catalogue.
ENISA Executive Director Juhan Lepassaar said: "The EU is now equipped with an essential tool designed to substantially improve the management of vulnerabilities."
Why it matters
Vulnerability scanners, patch tools, threat feeds and compliance checks all depend on CVE identifiers. If the programme had stopped, new flaws would have gone unnamed or been named inconsistently, making it harder to know what to patch first. The episode showed how much of global cyber defence rests on a small number of shared public services.
What it means for you
At home: nothing to do — but this is part of why automatic updates matter: they fix flaws without you needing to track them.
If you run a small business: ask your IT provider how they decide what to patch first. Good answers mention actively exploited vulnerabilities (CISA KEV or ENISA's EUVD) and internet-facing systems.
If you work in IT or at an MSP: avoid single points of failure in your vulnerability intelligence. Add the EUVD and vendor advisories alongside CVE/NVD feeds, and prioritise by known exploitation rather than severity scores alone.
The bottom line
The CVE programme survived, and the scare left the ecosystem more resilient: a foundation working on its independence and a second, European database. For defenders, the lesson is to know where your security data comes from — and to have a backup.
This article summarises and comments on the sources listed below. It is general information, not legal or professional advice.