Understand this story
On October 22, 2026, Computerworld published an article arguing that "the patch apocalypse is here," contending that the traditional model of patching everything on a fixed cadence is no longer sustainable and that organizations should shift to risk-based automated deployment. The article's stated background: nearly 48,000 CVEs were published in 2025, and the average time to exploitation has shrunk to about 5 days. It advocates prioritizing by risk rather than volume, addressing first the vulnerabilities in high-value assets that are being actively exploited and are reachable from the internet, and delegating browser patches, common third-party applications, and standard OS cumulative updates to automated staged deployment. The article also recommends running a tabletop exercise before the next emergency disclosure, noting that the bottleneck is often not the patching tools but incomplete asset data, unclear ownership, and slow handoffs between IT and security teams. This view is currently put forward in a single Computerworld report, with no subsequent developments of fact.
AI-generated from public reports
Latest development · Report
The Patch Apocalypse Is Here: Patching Everything Is Not the AnswerDevelopments
1 confirmed developments
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 22
Computerworld
The Patch Apocalypse Is Here: Patching Everything Is Not the Answer
Nearly 48,000 CVEs were published in 2025, and the average time to exploitation has shrunk to about 5 days, making the traditional model of patching everything on a fixed cadence unsustainable. The article argues for prioritizing by risk rather than volume, focusing first on vulnerabilities in high-value assets that are being actively exploited and are reachable from the internet, while delegating browser patches, common third-party applications, and standard OS cumulative updates to automated, staged deployment. It recommends running a tabletop exercise before the next emergency disclosure, because the bottleneck is often not the patching tools but incomplete asset data, unclear ownership, and slow handoffs between IT and security teams.