<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw" -->

---
title: The Vulnpocalypse - Good News and Bad News | daily.dev
description: AI tooling is driving a massive surge in discovered software vulnerabilities, creating what's called the 'vulnapocalypse.' Phil Venables argues the real...
canonical: https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The Vulnpocalypse - Good News and Bad News | daily.dev
og:description: AI tooling is driving a massive surge in discovered software vulnerabilities, creating what's called the 'vulnapocalypse.' Phil Venables argues the real...
og:url: https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw
og:image: https://api.daily.dev/og/posts/Pq5T6rBcW.png
og:image:alt: The Vulnpocalypse - Good News and Bad News
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The Vulnpocalypse - Good News and Bad News

**[Tech Lead Digest](https://daily.dev/sources/techleaddigest)** · 13 min read · 1 upvotes · 0 comments

## Summary

AI tooling is driving a massive surge in discovered software vulnerabilities, creating what's called the 'vulnapocalypse.' Phil Venables argues the real bottleneck isn't discovery or fixing code, it's deploying fixes across servers, edge devices, medical equipment, and other hard-to-reach infrastructure. He breaks remediation into four stages: discovery, fix development, testing and staging, and deployment, noting deployment is usually the hardest. Google is cited as an example of an organization that can push fixes rapidly, unlike most others. He proposes compensating controls, policy-intent systems, fast rollback, patchable architectures, and faster certification processes as ways to close the gap, calling for a shift from vulnerability management to full vulnerability operations.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.philvenables.com/post/the-vulnpocalypse-good-news-and-bad-news>

## Questions this post answers

### Why are so many more software vulnerabilities being discovered now that AI tooling is widely used?

AI tooling has dramatically increased the volume of vulnerabilities discovered in code bases, creating what's described as a 'deep clean' phase where long-standing latent vulnerabilities in existing code are surfaced faster than ever. This is driving increased workload for triage, even though many organizations are responding with improved speed, prioritization, and defense-in-depth practices.

_Teams rethinking triage workflows under this surge can follow practical vulnerability-operations approaches on daily.dev._

### What is the hardest stage of the vulnerability remediation process for most organizations?

Deploying the fix to every affected system is the hardest stage, harder than discovering, developing, or testing the fix. Challenges include cloud and on-premise dependencies, edge or device-specific constraints, equipment recertification requirements, intermittent connectivity, and the scale of pushing updates to thousands or millions of semi-managed devices.

_Engineers designing rollout and rollback strategies can track emerging patching architectures on daily.dev._

### What is a staged rollout strategy that reduces risk when deploying a security patch broadly?

Instead of jumping from a 5% sample deployment straight to 100%, roll out in increments such as 5%, 20%, 40%, 60%, 80%, then 100%, pausing and rolling back at any stage if significant issues occur. This guards against unrepresentative sampling, since teams often exclude critical systems from early test waves, and against race conditions from other concurrent updates.

_Those tuning deployment pipelines for safer patch rollouts can compare rollout tactics like this on daily.dev._

## Similar posts on daily.dev

- [Welcome to the vulnpocalypse, as vendors use AI to find bugs and patches multiply like rabbits](https://daily.dev/posts/welcome-to-the-vulnpocalypse-as-vendors-use-ai-to-find-bugs-and-patches-multiply-like-rabbits-u6ujg3xra) · The Register · 0 upvotes · 0 comments
- [You can't bug fix your way out of the vulnpocalypse · Alex Gaynor](https://daily.dev/posts/you-can-t-bug-fix-your-way-out-of-the-vulnpocalypse-alex-gaynor-kceilj0hu) · Lobsters · 3 upvotes · 1 comments
- [Beyond the Vulnerability Apocalypse: Scaling Your Basics and Vulnerability Management](https://daily.dev/posts/beyond-the-vulnerability-apocalypse-scaling-your-basics-and-vulnerability-management-q3uvzplzt) · Security Boulevard · 2 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#ai-security](https://daily.dev/tags/ai-security), [#devsecops](https://daily.dev/tags/devsecops)

[View this post on daily.dev](https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The Vulnpocalypse - Good News and Bad News","url":"https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw"},"datePublished":"2026-11-16T01:53:23.458Z","dateModified":"2026-11-16T02:04:18.001Z","description":"AI tooling is driving a massive surge in discovered software vulnerabilities, creating what's called the 'vulnapocalypse.' Phil Venables argues the real...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","isAccessibleForFree":true,"articleSection":"Tech Lead Digest","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Tech Lead Digest","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/6ed1ee1a2e5c49f698265a6b2912b80d","url":"https://daily.dev/sources/techleaddigest"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,ai-security,devsecops","timeRequired":"PT13M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Tech Lead Digest","item":"https://daily.dev/sources/techleaddigest"},{"@type":"ListItem","position":3,"name":"The Vulnpocalypse - Good News and Bad News"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-vulnpocalypse---good-news-and-bad-news-pq5t6rbcw#faq","mainEntity":[{"@type":"Question","name":"Why are so many more software vulnerabilities being discovered now that AI tooling is widely used?","acceptedAnswer":{"@type":"Answer","text":"AI tooling has dramatically increased the volume of vulnerabilities discovered in code bases, creating what's described as a 'deep clean' phase where long-standing latent vulnerabilities in existing code are surfaced faster than ever. This is driving increased workload for triage, even though many organizations are responding with improved speed, prioritization, and defense-in-depth practices. Teams rethinking triage workflows under this surge can follow practical vulnerability-operations approaches on daily.dev."}},{"@type":"Question","name":"What is the hardest stage of the vulnerability remediation process for most organizations?","acceptedAnswer":{"@type":"Answer","text":"Deploying the fix to every affected system is the hardest stage, harder than discovering, developing, or testing the fix. Challenges include cloud and on-premise dependencies, edge or device-specific constraints, equipment recertification requirements, intermittent connectivity, and the scale of pushing updates to thousands or millions of semi-managed devices. Engineers designing rollout and rollback strategies can track emerging patching architectures on daily.dev."}},{"@type":"Question","name":"What is a staged rollout strategy that reduces risk when deploying a security patch broadly?","acceptedAnswer":{"@type":"Answer","text":"Instead of jumping from a 5% sample deployment straight to 100%, roll out in increments such as 5%, 20%, 40%, 60%, 80%, then 100%, pausing and rolling back at any stage if significant issues occur. This guards against unrepresentative sampling, since teams often exclude critical systems from early test waves, and against race conditions from other concurrent updates. Those tuning deployment pipelines for safer patch rollouts can compare rollout tactics like this on daily.dev."}}]}
```

