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, 150 and 151, all released within the last month.
- Versions 149 and 150 alone 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 were rated with the highest severity ratings.
- Users should restart Chrome to pull in the update, which installs automatically in the background.
Google has patched an unusually large batch of security bugs in its Chrome browser: 1,442 in total, spread across three back-to-back releases. Chrome, for readers who mainly know it as the blue-red-yellow-green circle, is the world's most-used web browser, and the same engine sits under Microsoft Edge, Brave, Opera and others.
The scale here is the story. Chrome 149 and Chrome 150, both shipped last month, closed 1,072 flaws between them. That single pair of releases fixed more bugs than the previous 23 Chrome updates put together, according to figures Google published on Thursday and first reported by The Hacker News.
Chrome 151 followed on Wednesday, resolving another 370 issues. Of those, 349 were found by Google's own security teams rather than outside researchers. Seven carried the top severity ratings, meaning the underlying flaws could, in the wrong hands, let an attacker do serious damage to a machine that simply loaded a malicious web page.
Why are there suddenly so many fixes?
Google has not said the browser is under fresh attack. The jump reflects internal auditing work, not a wave of live exploitation. Almost all of the Chrome 151 fixes came from Google's own researchers, a signal that the company is running its bug-finding tools harder and shipping the results in bulk.
Browsers of Chrome's size are audited constantly by fuzzers, which are automated programs that hammer software with malformed inputs to see what breaks. A fuzzing run can surface hundreds of low-level memory bugs in a matter of days. Bundling those into one release, rather than dribbling them out, is a normal engineering choice.
None of the three advisories flag a zero-day, meaning a flaw already being used by attackers 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 only takes effect once you close and reopen it. Look for a small coloured arrow at the top right of the window; if it is there, 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 (the Chromium project), so the same fixes need to be repackaged and pushed by each vendor.
Common questions
Does a large patch mean Chrome is less safe than other browsers?
No. It means Google is finding and disclosing bugs at scale. A browser that ships no fixes is not safer, it is 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.
