AI Security
Google accelerates Chrome updates to twice weekly as AI-driven security flaws multiply
AI vulnerability detection is creating a surge in browser bugs, prompting Google to explore faster update schedules and seamless patching without restarts.
Ars Technica
The race to patch Chrome is accelerating. Google has observed a dramatic spike in identified vulnerabilities, driven largely by the ability of advanced AI models to automatically scan code and uncover flaws at scale—a shift that's forcing the company to rethink how quickly it rolls out updates.
AI is unearthing security issues at unprecedented speed#
Recent Chrome releases tell the story. Versions 149 and 150, delivered in June and early July, bundled together over 1,000 bug fixes—more fixes than the previous 23 releases contained combined. AI-powered security analysis is responsible for this influx, enabling researchers to detect vulnerabilities far faster than traditional manual review ever could. The stakes can be severe: one vulnerability discovered in recent analysis had persisted undetected for 13 years, and if exploited, could have allowed attackers to escape Chrome's sandbox and access local files on users' machines.
Moving toward more frequent updates#
To keep pace with the mounting threat landscape, Google is shifting its update cadence. The company announced a two-week release cycle earlier in 2026, but is now piloting an even more aggressive approach: updating Chrome twice per week. This accelerated schedule aims to narrow the window between vulnerability discovery and deployment, reducing the time attackers have to exploit new flaws before patches reach users.
The challenge of deployment without friction#
The traditional downside of more frequent updates is the disruption they cause. Each time Chrome updates, users often face restarts or interruptions. Google is actively developing mechanisms to deliver patches without requiring users to restart their browsers—a technical challenge, but one the company views as essential to scaling up its update frequency without creating user friction.

