It’s no longer safe to drink the free beer

Line chart of CVEs reported by year, 2014 to 2026. Roughly 6,000 to 8,000 a year through 2016, about 20,000 in 2021, 39,953 in 2024 and 48,152 in 2025. 2026 is at 77,847 as of October 13, with three months still to go.

Enterprises have been drinking the free beer of open source for decades, and most of the people maintaining it are volunteers who can’t keep up with this, so I think it’s time to start paying for the beer. Here’s the case Oren and I make:

  1. AI models can now turn a published fix into a working exploit within hours, and find new vulnerabilities at a scale human teams can’t match.
  2. “Patchmageddon” – the median time from disclosure to first exploitation went from about a year in 2021 to about a day in 2026, with one minute projected by 2027.
  3. Open source takes the first hit. Of 530 high- and critical-severity findings Anthropic reported to maintainers by May 2026, 75 had been patched.
  4. Enterprises should rely on professional open source, backed by a vendor or foundation with funded maintainers, staffed security response and an SLA, and move off dependencies with no identifiable maintainer.
  5. With exploits arriving within a day, the unpatched system is a bigger risk to keeping the business running than the patch.
  6. Pointing an existing artifact proxy at a supported source changes where open source comes from without changing build files, pipelines or developer habits. The proxy can also serve the nearest patched version automatically.
  7. Measure the time from disclosure to a deployed fix for your top 50 dependencies, record who maintains each critical one, and use AI to propose fixes while people review the merge.

We’ve seen this over the past year, first in Spring, and then over everything. And thanks to our long history with Bitnami, and some new work, we’ve got something to offer, some better beer than free beer. TrueSource Beer! (Also see the docs on it if you prefer that.)

Comments

Leave a Reply

Your post must include a link to this post.

How does this work?
Write a response on your own website and include a link to this post. Then submit your response’s URL here. Your response may appear here after moderation. To update or remove it, edit or delete your original post and submit the same URL again. Learn more about Webmentions.
Categories: