News · 17 April 2025
The CVE funding scare: why vulnerability identifiers are shared infrastructure
On 15 April 2025 news spread that the contract under which MITRE operates the Common Vulnerabilities and Exposures (CVE) programme was due to expire the following day. The US Cybersecurity and Infrastructure Security Agency (CISA) stepped in on 16 April with an eleven-month extension. Separately, a group of CVE board members announced plans for an independent foundation.
What CVE does
When someone discovers a security flaw, CVE gives it a unique identifier, such as CVE-2024-3094. That small convention underpins a great deal: scanners match software against identifiers, vendors publish advisories under them, compliance frameworks reference them, and security teams track their own remediation by them.
A world without a common identifier is one in which every vendor and tool uses its own names, and correlating "is this the same bug?" becomes slow and error-prone.
The lesson: know your single points of failure
Most organisations rely on this infrastructure without ever having evaluated it. The episode is a prompt to ask how your own security processes depend on external services.
- If your vulnerability scanner relies on a single feed, what happens if the feed is delayed?
- Do you cross-reference sources, such as vendor advisories, the CISA catalogue of known exploited vulnerabilities and your own testing?
- Can your team reason about risk when an identifier is missing?
Identifiers are not priorities
Another lesson is gentler. A CVE number says a flaw exists. It does not say whether it matters to you. Prioritisation requires context: is the vulnerable component reachable, is there a known exploit, is the data behind it valuable?
That is why we prefer validated findings. A scanner may report hundreds of identifiers; a human who checks reachability and impact can reduce that to the handful that need action this week. Penetration testing and attack-surface discovery work best when they are paired with that triage.
What to do this quarter
- List where vulnerability data enters your process, and add at least one independent source.
- Track exploited vulnerabilities, not just high scores.
- Record decisions: why a finding was accepted, mitigated or deferred.
Shared infrastructure deserves attention before it wobbles.
Written in April 2025; details reflect the situation at that time.