Update to Chrome 132 closes several security vulnerabilities

Google has released the new Chrome versions Chrome 132.0.6834.83/84 for Windows and macOS and 132.0.6834.83 for Linux. The installation of these updates eliminates 16 security vulnerabilities in the browser, which have apparently not yet been exploited for attacks. Version 132 also introduces some new features such as enhanced search with Google Lens. The manufacturers of other Chromium-based browsers will follow suit shortly.

In the Chrome Release Blog, Srinivas Sista lists the 13 of the 16 eliminated vulnerabilities that were discovered by external security researchers and reported to Google. Google categorizes five of these vulnerabilities as high risk. Google has awarded a total of $37,000 in rewards to those who discovered the vulnerabilities. As usual, Google is not commenting on the internally discovered vulnerabilities.

In the last update for Chrome 131, Google closed four vulnerabilities a week ago. As a rule, Chrome updates itself automatically when a new version is available. You can manually initiate the update check using the menu item Help > About Google Chrome (alternatively: Settings > About Google Chrome). Google has also released Chrome 131.0.6778.200 for Android. The Android version fixes the same vulnerabilities as the desktop version. Google plans to release the next major version, Chrome 133, on February 4.

New in Chrome 132

On the What’s New in Chrome, Google advertises the option to pin frequently used functions and shortcuts to the toolbar as buttons. You can also use Google Password Manager on Android and iOS to share passwords with family members (if you think that’s a good idea). On the desktop, you can use Google Lens to select any elements of a website (such as photos or videos) to start a Google search.

Other Chromium-based browsers

The manufacturers of other Chromium-based browsers are now called upon to follow suit with updates. Microsoft Edge, Vivaldi, Brave, and now also Opera are at the security level prior to the Chrome update described above.

Opera has had a very short time to catch up, as it only updated its browser a few hours before Google’s Chrome update and was thus on a par, at least for a short time. But now Opera will fall behind again, because with Opera 116 based on Chromium 131, the gaps to be plugged in Chrome/Chromium 132 remain untreated — there is no Extended Stable Channel in Chromium 131. Only the switch to Chromium 132 can help here, which Brave, Edge, and Vivaldi will undoubtedly do in the next few days.