Chrome May Move to Twice-Weekly Updates as AI Finds More Bugs
Google is piloting twice-weekly Chrome updates after AI security tools found 1,072 bugs in just two releases. Here's what changed and what it means for users.
Google is piloting a twice-weekly Chrome update schedule after AI-powered security analysis caused bug-fix counts to spike dramatically. Chrome 149, released in early June 2026, and Chrome 150, released just weeks later, together patched 1,072 vulnerabilities. That is more fixes than the previous 23 Chrome releases combined. Google says AI models can now probe software for flaws at a speed that also raises the risk of attackers using the same tools, making faster patching essential.
What happened
| Detail | Fact |
|---|---|
| Chrome 149 release | Early June 2026 |
| Chrome 150 release | A few weeks after Chrome 149 |
| Combined bug fixes (149 + 150) | 1,072 |
| Previous 23 releases combined | Fewer than 1,072 fixes |
| Oldest bug patched | 13 years in the codebase |
| New pilot update cadence | Twice per week |
Chrome 149 and Chrome 150 landed within weeks of each other in mid-2026, carrying a combined 1,072 bug fixes. To put that in perspective, Google says those two releases patched more issues than the 23 milestones before them put together. The driver is large AI security models that scan software for vulnerabilities far faster than human researchers can.
One of the patched bugs had sat unnoticed in Chrome’s code for 13 years. According to Google, if it had been exploited, an attacker could have bypassed the Chrome sandbox (the security layer that isolates the browser from the rest of your operating system) and made the browser read local files on a user’s machine.
Why does Chrome’s update speed matter for businesses?
The same AI tools that help Google find flaws can, in principle, help attackers find them too. Google’s concern is that the gap between a vulnerability being discovered and a patch reaching users needs to shrink. A browser that sits on an older version for even a few days is a wider target.
For businesses running managed Chrome deployments, faster releases also mean more testing overhead. An IT team that used to validate a new Chrome build every four weeks now faces a schedule that could demand twice-weekly review cycles. That is a real operational cost, even if the security payoff is clear.
The restart problem is also worth noting. Most Chrome updates apply when the browser relaunches, which means users who leave tabs open for days can drift out of date without realising it. Google is reportedly working on a delivery mechanism that applies updates without requiring a restart, which would close that gap automatically.
Our take
The 1,072-fix number is striking, but the more important signal is structural: AI has changed the economics of vulnerability research permanently. Finding bugs used to be the bottleneck. Shipping patches fast enough is now the bottleneck. Google’s move to a two-week cycle earlier in 2026 was already aggressive by historical standards. Twice per week is genuinely new territory for a consumer browser at this scale.
For most business owners, the practical change is small right now. Chrome updates quietly in the background and a no-restart delivery system would make that even more seamless. But if you run any kind of web application or rely on browser-based tools for your team, it is worth knowing that the browser your users run is about to change more often. Testing critical workflows against Chrome beta builds periodically is cheap insurance.
The broader pattern here connects to how AI is accelerating every part of the security cycle, not just patching. If you are thinking about AI integration for your own business processes, security tooling is one of the areas with the most near-term, measurable payoff. We have been tracking this shift across our AI news coverage and the pace is not slowing.
What to do about it
- Check that Chrome auto-updates are enabled across all business devices. Go to chrome://settings/help to confirm the current version.
- Encourage staff to relaunch Chrome at least once a day so pending updates apply. Until a no-restart system ships, this is the simplest mitigation.
- If you manage Chrome via policy (Google Admin Console or MDM), review your update deferral settings. A week-long delay made sense on a four-week cycle; it matters more on a twice-weekly one.
- Add a quarterly check of Chrome release notes to your security routine so critical-severity fixes get flagged to your team quickly.
Faster patching only works if the patch actually lands on your users’ machines. Make sure it does.
Frequently asked questions
How many bugs were fixed in Chrome 149 and Chrome 150?
Chrome 149 and Chrome 150 together fixed 1,072 bugs, which Google says is more than the previous 23 Chrome releases combined.
Why is Google speeding up Chrome updates?
AI security models can now scan software for vulnerabilities much faster than before. Google is concerned that attackers could use the same AI tools, so it wants patches to reach users faster to close the window of exposure.
Will Chrome updates require a restart?
Currently most Chrome updates apply when the browser relaunches. Google is working on a system to deliver updates without requiring a restart, though it has not confirmed a release date.
How often will Chrome update under the new schedule?
Google announced a two-week update cycle earlier in 2026 and is now piloting a system that would push updates twice per week.