Google patched over 1,000 Chrome bugs in two releases using AI — more than the previous 23 milestones combined
Google says large language models now handle nearly every stage of Chrome's vulnerability management pipeline, from discovery to patch generation.
What matters
- Google patched 1,072 security bugs across Chrome 149 and 150, exceeding the total fixed in the previous 23 Chrome milestones combined.
- LLMs are now used across Chrome's entire vulnerability management pipeline: discovery, reproduction, severity assessment, developer assignment, patch generation, and test creation.
- Google's AI security tooling evolved from LLM-assisted fuzzing (2023) to Project Zero's Naptime, then Big Sleep with DeepMind, and a Gemini-powered agent harness in early 2026.
- CVE-2026-15903, a high-severity V8 RCE flaw affecting Chrome versions prior to 150.0.7871.128, was disclosed on July 23, 2026.
- The trend mirrors similar AI-assisted bug-finding efforts at Microsoft, suggesting an industry-wide shift in vulnerability management.
Security advisory
- CVE:
- CVE-2026-15903
- Severity:
- High
- Affected:
- Google Chrome desktop versions prior to 150.0.7871.128; Chromium-based browsers embedding the affected V8 engine; all operating systems (Windows, macOS, Linux) shipping vulnerable Chrome versions
- Patch status:
- Patched in Chrome 150.0.7871.128
What happened
Google says artificial intelligence is dramatically accelerating its ability to find and fix security vulnerabilities in Chrome. Across the browser's two most recent stable releases — Chrome 149 and Chrome 150 — Google patched 1,072 security bugs, a figure the company says surpasses the total number fixed across the previous 23 Chrome milestones combined.
The scale of this jump stems from Google's expanding use of large language models throughout the vulnerability management pipeline. According to the company, LLMs are now involved in discovering flaws, reproducing bug reports, determining severity, assigning bugs to developers, generating candidate patches, and creating tests.
Google's AI-driven security push has been building for several years. The company began using LLMs to improve security fuzzing in 2023. It then worked with Project Zero on Naptime, a system that gave AI models specialized vulnerability research tools. That effort evolved into Big Sleep, an AI-powered vulnerability discovery agent developed with Google DeepMind and Project Zero, which 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.
The news comes alongside a separate but related security development: CVE-2026-15903, a high-severity remote code execution flaw in Chrome's V8 JavaScript engine, was disclosed on July 23, 2026. The out-of-bounds read and write vulnerability affects Chrome versions prior to 150.0.7871.128 and allows a remote attacker to execute arbitrary code inside the browser sandbox through a crafted HTML page. While exploitation requires user interaction, such renderer-sandbox flaws are frequently chained with sandbox escapes for fuller compromise.
Why it matters
The 1,072-bug figure is a striking data point in an emerging trend: AI is not just helping companies write code faster — it is fundamentally changing how fast they can find and fix the mistakes in that code. As experts have warned for the last two years, companies like Microsoft and now Google are discovering and patching an exponential number of bugs thanks to LLMs and AI-assisted tooling.
For Chrome users, this means a more rapidly hardened browser. For the broader security community, it signals that AI-augmented vulnerability discovery is moving from experimental to operational. Google's pipeline — where AI agents discover, triage, patch, and test bugs — could become a template for other large software projects.
However, the same dynamics raise questions. If AI can find bugs at this scale for defenders, it can presumably do the same for attackers. The disclosure of CVE-2026-15903 is a reminder that serious vulnerabilities in widely deployed engines like V8 remain a live concern, even as AI-assisted patching accelerates.
What to watch
- Whether Google's AI-assisted bug-finding approach extends beyond Chrome to other major Google products such as Android or Google Cloud Platform.
- How the broader industry — Microsoft, Apple, Mozilla — responds in terms of disclosing AI-assisted vulnerability metrics of their own.
- Whether the increase in discovered bugs reflects a genuine improvement in security or partly an increase in lower-severity findings that AI surfaces more readily.
- The evolving threat landscape: as AI tools democratize vulnerability discovery, defenders and attackers may both scale, potentially reshaping the economics of exploitation.
What to do next
Developers
Audit your own CI/CD pipeline for opportunities to integrate LLM-assisted fuzzing, triage, and patch-generation tooling similar to Google's approach.
Google's results show AI can scale vulnerability discovery and remediation across a massive codebase; smaller teams may see proportional gains.
Founders
Evaluate whether AI-assisted security tooling can be a differentiator or cost-saver for your product, especially if you ship a large codebase or browser-based software.
The gap between AI-augmented and manual security workflows is widening rapidly; early adoption could reduce both breach risk and engineering cost.
PMs
Track the ratio of AI-discovered vs. manually reported bugs in your product and set targets for increasing AI-assisted coverage over the next two quarters.
Google's 1,072-bug milestone demonstrates that measurable AI-assisted security metrics are becoming a credible signal of product maturity.
Investors
Monitor startups building AI-powered vulnerability discovery, triage, and patch-generation platforms; the Chrome results validate the market thesis at enterprise scale.
Google's internal results provide strong evidence that AI security tooling delivers outsized ROI, which should drive demand for third-party equivalents.
Operators
Ensure your organization updates Chrome to version 150.0.7871.128 or later to mitigate CVE-2026-15903 and benefit from the 1,072 AI-discovered patches.
A high-severity V8 RCE flaw remains exploitable on unpatched versions, and the latest release includes the largest batch of security fixes in Chrome's recent history.
Testing notes
Caveats
- Google's AI-assisted vulnerability pipeline is an internal toolset and is not publicly available for external testing.
- The 1,072-bug figure and methodology are vendor-reported; no independent verification of the count or severity distribution is available from the supplied sources.
- CVE-2026-15903 can be verified by checking Chrome version and reviewing the SentinelOne advisory, but active exploitation testing should only be conducted in controlled environments.