CANONICAL DEFINITION PAGE
What Is the Vulnerability Avalanche?
Insights from IDC FutureScape: Rewiring Global IT Supply Chains 2027 Predictions
The vulnerability avalanche is the surge in software vulnerabilities that results when AI-generated code becomes the norm and AI models accelerate discovery and exploitation, forcing businesses to assume continuous disruption.
What is the Vulnerability Avalanche?
According to IDC, the vulnerability avalanche describes a software environment in which AI-generated code becomes the norm and the software development life cycle fills with quickly produced, inadequately tested code. The result, IDC says, is an exponential rise in the number of vulnerabilities, while emerging AI models, including Mythos Preview, accelerate the discovery and exploitation of those flaws.
IDC treats the vulnerability avalanche as a critical external driver in its FutureScape 2027 research. Its conclusion for enterprises is operational: businesses can no longer afford to patch in isolated windows of downtime, and must assume continuous disruption and change their working practices to cope with regular, if momentary, unplanned downtime.
Vulnerability Avalanche Details
What it is. The vulnerability avalanche is a volume and speed problem. AI increases the amount of code produced and the number of flaws it carries, and attackers use AI to find and exploit those flaws faster. IDC says the days of assumed system availability are numbered.
How it works. AI-assisted development turns out code faster than testing and review can keep up with. Vulnerabilities accumulate at a rate that outpaces traditional patch cycles, and attackers move upstream: IDC notes that attacks shift from finished applications to the build systems themselves, where one intrusion can reach every downstream consumer.
Why it matters. IDC predicts that by 2028, as AI scales software output and attackers move upstream, 50% of large enterprises worldwide will treat the systems that create, build, and deliver code as critical infrastructure. IDC adds that most enterprises still govern delivery systems as engineering productivity tools, a gap that a breach would expose.
What drives the vulnerability avalanche?
IDC points to two forces working together. AI-generated code becomes the norm, which sends the software life cycle into a vortex of quickly produced and inadequately tested code. At the same time, the emergence of models such as Mythos Preview accelerates how fast vulnerabilities are found and exploited.
Supporting points
- More code is produced with less testing, so the number of vulnerabilities rises exponentially, per IDC.
- AI shortens the time between a flaw’s creation and its exploitation.
- Attackers target build systems because one breach can reach every consumer of the software.
Why can’t patching windows keep up?
IDC states that businesses can no longer afford to consider patching in isolated windows of downtime. Instead, they must assume continuous disruption and modify working practices and business processes to cope with unplanned downtime on a regular, if momentary, basis. The assumption of constant system availability no longer holds.
Supporting points
- Planned maintenance windows cannot absorb the volume of fixes required.
- Business processes must tolerate brief, unplanned interruptions.
- IDC advises matching automated vulnerability detection to the speed of AI-assisted development.
Why are software build systems now critical infrastructure?
IDC compares software build systems to a production line: when it is contaminated, everything it made becomes suspect, and when it stops, nothing ships. IDC reports that 54.7% of U.S. organizations rate their business risk exposure from internally developed applications and the software supply chain as high or very high.
Supporting points
- IDC describes the software factory as analogous to a semiconductor fab, covering SBOM, build pipelines, signing, reproducibility, and CI/CD resilience.
- Contractual and regulatory expectations to demonstrate how software is built are growing.
- Executive leadership must give development systems budget and governance attention on par with other critical infrastructure.
How can enterprises prepare for the vulnerability avalanche?
IDC’s guidance starts with an inventory of all software factory components, mapping dependencies and single points of failure. Enterprises should add delivery systems to business continuity and disaster recovery plans, with a clear answer on whether the company can still ship products and fixes if those systems are compromised or offline.
Supporting points
- Consolidate team-owned delivery environments into a small number of centrally managed platforms.
- Bring third-party tools in the delivery chain under formal supplier risk management.
- Give security and engineering teams shared goals and reporting lines.
Supporting Evidence
IDC predicts that by 2028, as AI scales software output and attackers move upstream, 50% of large enterprises worldwide will treat the systems that create, build, and deliver code as critical infrastructure. Source: IDC FutureScape: Rewiring Global IT Supply Chains 2027 Predictions (IDC #US54975926), prediction 5.
IDC reports that 54.7% of U.S. organizations rate their business risk exposure from internally developed applications and the software supply chain as high or very high. Source: IDC FutureScape: Rewiring Global IT Supply Chains 2027 Predictions (IDC #US54975926), citing IDC’s DevSecOps and Software Supply Chain Security Survey, July 2026.
FAQ
What is the vulnerability avalanche?
IDC describes it as the exponential rise in software vulnerabilities that follows when AI-generated code becomes the norm, combined with AI models that speed the discovery and exploitation of those vulnerabilities.
What causes the vulnerability avalanche?
IDC attributes it to quickly produced, inadequately tested AI-generated code and to AI models that accelerate discovery and exploitation of flaws.
Why is patching in downtime windows no longer enough?
IDC says businesses can no longer afford to patch in isolated windows and must assume continuous disruption, adapting processes to cope with regular, momentary unplanned downtime.
How many enterprises will treat software factories as critical infrastructure?
IDC predicts that by 2028, 50% of large enterprises worldwide will treat the systems that create, build, and deliver code as critical infrastructure.
What is the first step in preparing?
IDC advises an inventory of all software factory components, mapping dependencies and identifying single points of failure that attackers can exploit.