Google has fixed 1,442 Chrome security flaws across three recent browser releases, highlighting the growing pressure technology companies face as artificial intelligence accelerates vulnerability discovery.
The total includes 1,072 bugs resolved in Chrome versions 149 and 150, which were released in June. Those two releases alone addressed more vulnerabilities than Google had fixed across the previous 23 major Chrome updates combined.
Google followed them with Chrome 151, released on Wednesday, July 29, 2026. That update corrected another 370 security weaknesses.
Of the vulnerabilities fixed in Chrome 151, Google researchers identified 349 internally. Seven were classified as critical, the highest severity level used for software security flaws.
The sharp rise shows how quickly the cybersecurity landscape is changing. AI systems can now review large amounts of code, detect weaknesses and generate bug reports far faster than traditional research methods.
AI drives surge in Chrome security flaws
Large language models are transforming vulnerability research by helping security teams examine complex software code at greater speed.
This technology can uncover weaknesses that may have remained hidden for years. However, it is also creating a challenge for software companies because new problems are being reported faster than developers can investigate, patch and disclose them.
The wider vulnerability market has experienced a similar increase.
Figures published by the U.S. National Vulnerability Database show that 46,872 security flaws had been recorded in 2026 by the end of July. That figure is already approaching the 49,920 vulnerabilities reported during all of 2025.
The rapid increase does not necessarily mean that software is suddenly less secure. It also reflects stronger detection tools, automated testing and increased use of AI in cybersecurity research.
Gemini finds 13-year-old Chrome weakness
One notable Chrome security flaw discovered using AI was a critical sandbox escape vulnerability in the browser’s Navigation component.
Tracked as CVE-2026-3545, the flaw received a severity score of 9.6 out of 10. Google patched it in March 2026.
The vulnerability could have allowed an attacker to manipulate Chrome into accessing local files stored on a user’s device.
Google said the weakness was found through an automated agent system powered by its Gemini AI models. The bug had reportedly remained undetected in Chrome’s source code for more than 13 years.
The discovery demonstrates the potential value of AI-assisted security research. Automated agents can repeatedly test software behavior and examine code patterns that human researchers may overlook.
Google accelerates Chrome security updates
Google is changing how frequently it releases Chrome updates as it responds to faster, AI-assisted cyberattacks.
The company is moving toward a two-week schedule for major Chrome versions while continuing to issue weekly security patches.
It is also testing two security releases every week. The goal is to reduce the time between the discovery of a vulnerability and the delivery of a working fix to users.
Faster updates could make it harder for attackers to exploit publicly known weaknesses before people receive protection.
Google said it remains committed to publicly documenting security flaws that affect the stable version of Chrome. This includes vulnerabilities discovered by internal teams and those reported by outside researchers.
The company is also developing automated systems that can prepare release notes and descriptions for Common Vulnerabilities and Exposures, commonly known as CVEs.
Automating this work may reduce administrative delays and allow security teams to publish important information more quickly.
Chrome patches could arrive without restarts
Installing browser updates often requires users to restart Chrome. Many people delay that step because they do not want to close active tabs or interrupt their work.
Google is exploring dynamic patching as a possible solution.
The technology would use Chrome’s multi-process design to replace background processes with updated versions while the browser remains open. These could include the renderer and graphics processing unit processes.
This approach may allow some security fixes to take effect without requiring a full browser restart.
Google is also improving the way Chrome restores browsing sessions when a restart remains necessary.
Chrome 150 introduced one such improvement for macOS. Applications on Apple computers often continue running in the background after users close every visible window.
Chrome can now detect a waiting update during this windowless state and restart automatically, allowing the update to take effect without disrupting an active browsing session.
Google targets entire classes of security bugs
Google is not only fixing individual Chrome security flaws. It is also working to eliminate common categories of vulnerabilities from the browser.
Many serious software weaknesses are linked to memory management problems in C++, the programming language traditionally used for much of Chrome’s code.
These issues include use-after-free errors, out-of-bounds access and other memory safety failures. Attackers may exploit such flaws to crash software, expose information or execute unauthorized instructions.
Google is strengthening Chrome’s runtime protections to reduce the danger caused by older C++ code.
The company is also increasing its use of Rust, a programming language designed to provide stronger memory safety protections.
In addition, Google is building parts of Chrome’s main user interface with HTML, CSS and TypeScript. This could further reduce the browser’s reliance on traditional C++ frameworks.
Third-party Chrome software to receive faster updates
Chrome depends on software components created and maintained by outside developers.
Outdated third-party code can expose the browser to vulnerabilities even when Google’s own code remains secure.
To reduce this risk, Google plans to place all third-party Chrome dependencies on automated update systems. These pipelines will help ensure that external components receive newer and more secure versions without lengthy manual processes.
The company hopes this strategy will close another potential route that attackers could use to compromise the browser.
Why Chrome users should install updates quickly
The growing number of Chrome security flaws makes timely browser updates increasingly important.
Finding a vulnerability is only part of the security process. A patch must also be developed, released and installed before attackers begin exploiting the weakness.
Users should keep Chrome’s automatic update function enabled and restart the browser when prompted. They can also check for pending updates through Chrome’s settings menu.
Google’s faster release schedule, dynamic patching research and growing use of memory-safe technology could make future updates less disruptive.
However, browser security still depends on users receiving and applying fixes before criminals can take advantage of newly discovered vulnerabilities.
As AI improves the speed of both defensive research and cyberattacks, the race to discover and patch Chrome security flaws is likely to become even more intense.
