Three Recent Chrome Releases Fix 1,442 Flaws, More Than Prior 23 Updates Combined
14:51 · July 31, 2026 · Hacker News AI Section

Google on Thursday announced that it fixed a whopping 1,072 security bugs in Chrome versions 149 and 150, surpassing the total number of flaws the company fixed across the prior 23 milestones combined. Both versions were released last month. In its latest patch for Chrome 151, released Wednesday, the tech giant resolved 370 flaws, out of which 349 were reported by Google itself. Seven of the
Summary
Google has addressed a total of 1,442 security vulnerabilities across Chrome versions 149, 150, and 151. The first two releases alone accounted for 1,072 issues, exceeding the combined fixes from the preceding 23 milestones, while the 151 update resolved 370 additional flaws, seven of them rated critical. Most of the work in the latest cycle originated from internal discovery rather than external reports.
The increase stems from wider adoption of large language models that speed up code analysis and bug identification. Google used an agent harness built on its Gemini models to locate a sandbox escape flaw (CVE-2026-3545) in the Navigation component that had gone unnoticed for more than 13 years; the vulnerability could have allowed an attacker to read local files. National vulnerability statistics show a similar pattern industry-wide, with 46,872 entries recorded so far in 2026.
To keep pace with faster discovery, Google is moving from weekly security updates to a pilot of two releases per week while maintaining its two-week major-version cadence. The company is also automating the creation of release notes and CVE descriptions to shorten the interval between fix and disclosure. In parallel, it is testing dynamic patching that replaces background processes such as the renderer and GPU without a full browser restart, using Chrome’s multi-process design and platform-specific behaviors such as macOS background execution.
Longer-term efforts focus on removing entire classes of memory-safety problems. These include runtime hardening, wider use of Rust for new components, and rewriting the top-level interface in HTML, CSS, and TypeScript. Third-party dependencies are being moved to automated update pipelines. The Chrome Security Team notes that the goal is to deliver fixes faster than adversaries can exploit them while reducing the operational burden on users.
Why it matters
This article highlights how AI and LLMs are fundamentally changing the cybersecurity landscape by accelerating vulnerability discovery and exploitation. Dutch security professionals must adapt their vulnerability management strategies to handle the increased volume of AI-driven threat disclosures in ubiquitous enterprise software.










