Google Patches 1,442 Chrome Flaws Across Three Releases, More Than the Prior 23 Combined
Chrome 149, 150 and 151 together resolved more security bugs than nearly two years of previous updates, with Google's own researchers flagging the bulk of the issues.
Key points
- Google fixed 1,442 security bugs across Chrome versions 149 through 151, all released within the last month.
- Chrome 149 and 150 together accounted for 1,072 fixes, more than the previous 23 Chrome updates combined.
- Chrome 151, released Wednesday, patched 370 flaws, with 349 reported by Google's own researchers.
- Seven of the Chrome 151 bugs carried the highest severity ratings.
- Restart Chrome to apply the update, which installs silently in the background but won't take effect until the browser closes.
Google has patched 1,442 security bugs in Chrome across three back-to-back releases. Chrome is the world's most-used web browser, and its underlying engine powers Microsoft Edge, Brave, Opera and Vivaldi.
The scale is the story. Chrome 149 and 150, both shipped last month, closed 1,072 flaws between them. That pair alone fixed more bugs than the previous 23 Chrome updates combined, per figures Google published Thursday and first reported by The Hacker News. We covered each release separately: our 20 July story on Chrome 150's seven memory safety bugs noted that all were found internally, and our 30 July report on Chrome 151's 370 fixes called it one of Google's largest single releases of the year. Seen together, the three releases represent a shift in how aggressively Google is bundling its internal audit output.
Of the Chrome 151 fixes, seven carried the top severity ratings. A flaw at that level could, in the wrong hands, let an attacker cause serious damage to a machine that simply loaded a malicious page.
Why are there suddenly so many fixes?
Google hasn't said the browser is under fresh attack. The jump reflects internal auditing, not live exploitation. Nearly all the Chrome 151 fixes came from Google's own teams, a signal that the company is running its bug-finding tools harder and shipping results in bulk.
Browsers Chrome's size are audited constantly by fuzzers: automated programs that hammer software with malformed inputs to find what breaks. A fuzzing run can surface hundreds of low-level memory bugs in days. Bundling them into one release rather than pushing them piecemeal is a routine engineering choice, not a sign of crisis.
None of the three advisories flag a zero-day, meaning a flaw already exploited before a patch existed. That distinguishes this batch from the emergency Chrome updates Google has pushed several times this year.
What should ordinary users do?
Restart the browser. Chrome updates itself quietly in the background, but the new version takes effect only once you close and reopen it. A small coloured arrow at the top right of the window means an update is waiting.
| Release | Bugs fixed | Notes |
|---|---|---|
| Chrome 149 and 150 (combined) | 1,072 | Released last month |
| Chrome 151 | 370 | Released Wednesday; 349 found by Google |
| Prior 23 Chrome updates (combined) | Fewer than 1,072 | Baseline for comparison |
Edge, Brave, Opera and Vivaldi users should watch for their own updates in the coming days. Those browsers share Chrome's underlying code via the Chromium project, so each vendor must repackage and push the same fixes independently.
Common questions
Does a large patch mean Chrome is less safe than other browsers?
No. It means Google's finding and disclosing bugs at scale. A browser that ships no fixes isn't safer, it's simply quieter about what it finds.
Do I need to do anything if Chrome is set to auto-update?
You still need to restart the browser for the update to apply. Leaving tabs open for weeks is the most common reason users stay on an old, vulnerable build.
