The AI security crisis may not begin with a superintelligent system escaping control. It may arrive as an overwhelming flood of ordinary software bugs discovered faster than people can investigate, prioritize, patch, and deploy fixes. In this episode of The Daily AI Chat, we examine WIRED’s September 19, 2026 report by Matt Burgess and Lily Hay Newman on the rapid rise of AI-assisted vulnerability discovery—and why the bottleneck is shifting from finding flaws to fixing them.The numbers are startling. Microsoft reportedly issued patches for 974 common vulnerabilities and exposures in a single month. Oracle shipped 1,448 patches in July, compared with 309 in July 2025. Two major Google Chrome releases included 1,072 patches, more than the total vulnerability fixes delivered across the previous 23 major releases. Mozilla said an AI-assisted Firefox bug-hunting sprint uncovered 271 vulnerabilities.On one level, this is exactly what security teams have wanted. Finding a flaw before criminals exploit it can prevent breaches, ransomware, espionage, and costly emergency response. AI systems can analyze vast codebases, identify suspicious patterns, test unusual execution paths, and help researchers surface weaknesses that might otherwise remain hidden for years. Faster discovery can make software safer—if organizations have enough capacity to handle the results.That condition is the heart of the problem. Every credible report still needs human attention. Engineers must reproduce the issue, determine whether it is genuinely exploitable, assess its severity, identify affected versions, coordinate with vendors, design a fix, test for regressions, publish guidance, and persuade users and administrators to install the update. A machine can generate hundreds or thousands of findings quickly, but remediation remains tied to people, process, release schedules, and the risk of breaking systems that businesses depend on.We explain how AI changes the economics of vulnerability research. The cost of searching falls dramatically, while the cost of triage can rise. Security teams may receive more valuable discoveries alongside duplicates, false positives, incomplete reports, and automatically generated noise. Attackers gain access to many of the same tools, creating a race between defensive researchers and criminals who want to weaponize a flaw before a patch is ready.Open-source maintainers are particularly exposed. Much of the digital economy depends on libraries and projects maintained by small teams or unpaid volunteers. Those maintainers may suddenly face a surge of machine-generated reports without the staff, funding, or infrastructure needed to evaluate them. Even accurate findings can become harmful when disclosure is poorly coordinated or when public details appear before downstream users have time to update.This episode explores what a serious response should look like. Organizations need automated systems that can deduplicate reports, rank likely severity, connect findings to deployed assets, and help engineers focus on the issues that matter most. Vendors need clearer disclosure channels and realistic response timelines. Governments and large technology companies need to fund the open-source projects they rely on. Development teams must invest in memory-safe languages, secure design, code review, reproducible builds, rapid patch pipelines, and better inventories of their software dependencies.AI itself will be part of the defense. Models can help validate findings, propose patches, generate tests, monitor regressions, and explain risk to administrators. But adding more automation without strengthening the human and institutional layer could simply accelerate the flood. The goal is not to stop finding vulnerabilities; it is to ensure that discovery produces safer systems instead of an unmanageable backlog.Source: WIRED, September 19, 2026. Reporting by Matt Burgess and Lily Hay Newman.