Google says artificial intelligence is dramatically increasing the number of security vulnerabilities it can find and fix in Chrome, with more than 1,000 security bugs patched across the browser's two most recent releases as it expands its use of AI.
According to Google, Chrome 149 and Chrome 150 fixed 1,072 security bugs, surpassing the total number fixed across the previous 23 Chrome milestones combined.
The company says it now uses large language models throughout the vulnerability management process, including discovering flaws, reproducing reports, determining severity, assigning bugs to developers, generating candidate patches, and creating tests.
Google began using LLMs to improve security fuzzing in 2023 before working with Project Zero on Naptime, a system that provided AI models with specialized vulnerability research tools.
The company later collaborated with Google DeepMind and Project Zero on Big Sleep, an AI-powered vulnerability discovery agent that found flaws in Chrome’s V8 JavaScript engine and graphics components.
In early 2026, Google created a Gemini-powered agent harness to search the broader Chrome codebase for vulnerabilities while reducing false positives.
One vulnerability discovered by the system was a Chrome sandbox escape that had remained in the codebase for more than 13 years. If exploited, the flaw would have allowed a compromised renderer to escape the sandbox and trick the browser into reading local files.
Google is also encouraging its developers to add SECURITY.md files describing trust boundaries and threat models, helping its AI systems better identify operations with security implications.
The company says its multi-agent AI workflows help rather than replace existing security testing, including fuzzing, which remains effective at discovering complex vulnerabilities.
Google has also seen a sharp increase in reports submitted through the Chrome Vulnerability Reward Program, and by March 2026, the company had received more security bug reports than during all of 2025.
This prompted Google to modify its program to prioritize reports that add to what its already finding and processing through its automated tooling.
The company is also automating vulnerability triage, including filtering spam and duplicates, reproducing proof-of-concept exploits, assigning severity ratings, and routing reports to the appropriate developers.
Google estimates that this automated process saves hundreds of hours of developer time each month.
After a vulnerability is confirmed, fixing agents generate multiple potential patches, while another agent evaluates the proposed fixes and produces additional information for developers to review.
In May, these systems reportedly prevented more than 20 vulnerabilities from reaching production, including one issue classified as critical.
However, Google says finding and fixing vulnerabilities more quickly also requires accelerating how patches are delivered to users.
Once a security fix is committed to Chrome’s public source code, attackers can inspect the change and attempt to reverse-engineer the vulnerability before the update reaches users.
Google is also transitioning Chrome to a two-week major release cycle with weekly security updates and is piloting two security releases per week to reduce this patch gap.
To reduce disruptions, the company is developing "dynamic patching," which would allow Chrome to apply updates without restarting the browser.
Starting with Chrome 150 on macOS, the browser can automatically restart to apply a pending update when it is running in the background without any open windows.
Google says its long-term goal is to keep Chrome continuously updated through dynamic patching, automatic restarts during periods of inactivity, and improved session restoration.
Test every layer before attackers do
Security teams log 54% of successful attacks and alert on just 14%. The rest move through your environment unseen.
The Picus whitepaper shows how breach and attack simulation tests your SIEM and EDR rules so threats stop slipping by detection.
Get the whitepaper
Post a Comment Community Rules
You need to login in order to post a comment
Not a member yet? Register Now