Chrome is about to update twice a week, thanks to AI finding more bugs than ever
Google's AI security tools spotted more flaws in two recent Chrome releases than in the previous 23 combined. That is a lot of patches, and they may soon land silently in the background.
Key points
- Chrome 149 and Chrome 150, released in early June 2026, together fixed 1,072 security bugs, more than the previous 23 Chrome releases combined.
- A single bug that AI tools uncovered had been hiding in Chrome's code for 13 years.
- Google is piloting twice-weekly Chrome updates to keep pace with the speed at which AI can now find and exploit software flaws.
- Google is working on a way to deliver those updates silently, without asking you to restart your browser.
Google's Chrome browser already updates faster than almost anything else on your computer. Now, as first reported by Ars Technica, that pace is about to get considerably quicker, and the reason is AI.
What exactly happened?
Two recent Chrome releases, versions 149 and 150, arrived just weeks apart in early June 2026. Together they fixed 1,072 security bugs. That is more patches than the previous 23 Chrome updates added up.
One of those bugs had sat unnoticed in Chrome's code for 13 years. If someone had found and exploited it, they could have broken out of Chrome's sandbox (the walled-off area that stops the browser touching the rest of your computer) and read local files on your machine. Nasty.
The reason so many bugs surfaced so quickly is that Google is now using large AI security models, software trained to scan code and hunt for weaknesses the way a very fast, very tireless human reviewer would. These tools can probe millions of lines of code in the time it would take a person to check a few hundred.
Should I be worried?
Not immediately, but there is a real concern driving this change. If Google's AI can spot flaws this fast, attackers using similar tools can too. The quicker a bug is found, the shorter the window before someone tries to use it against real browsers.
Google's answer is speed. The company moved Chrome to a two-week update cycle earlier in 2026. Now it is testing twice-weekly releases, so patches ship before bad actors have much chance to act on what they find.
What does this mean for you, practically?
More frequent updates could mean more prompts to restart Chrome. Google knows that is annoying, and it is actively working on a system that would apply updates silently in the background, no restart required.
For now, the best thing you can do is let Chrome update whenever it asks. If you see a small arrow in the top-right corner of your browser, that means an update is ready. Click the three-dot menu, choose Help, then About Google Chrome, and it will finish the job in about 30 seconds.
| Chrome release | Bug fixes |
|---|---|
| Chrome 149 (June 2026) | Part of 1,072 combined |
| Chrome 150 (June 2026) | Part of 1,072 combined |
| Previous 23 releases | Fewer than 1,072 total |
One privacy note worth knowing: Chrome's update process contacts Google's servers to check for and download patches. That is standard and expected behaviour, but if you use a privacy-focused browser fork, check whether it gets these security fixes at the same pace.
Common questions
Will my Chrome restart automatically without warning?
Google is working toward background updates, but right now Chrome still asks before restarting. You can click later and it will apply the update next time you close the browser normally.
Does this affect Chrome on phones too?
Mobile Chrome updates go through the App Store or Google Play rather than Chrome's own update system, so the twice-weekly rollout applies mainly to desktop versions first.
