Reported by 2 outlets

Google ships Chrome 157 to resolve hundreds of security bugs and streamline tab sharing

PCWorld

The story so far

AI summary of the reporting below · Updated · How we work

Google has launched Chrome 157.0.8103.38/39 for Windows and macOS and 157.0.8103.38 for Linux, addressing 213 security vulnerabilities. According to Google, none of the patched weaknesses have been actively exploited in the wild yet. The release includes seven critical flaws alongside 77 high-risk, 75 medium-risk, and 54 low-risk bugs. Google identified 130 issues internally and has paid external researchers $31,000 in bug bounties for discovering the remainder. [1][2]

The update primarily remedies memory safety problems, including 45 use-after-free bugs, four of which rank as critical, as well as 13 data leaks and 13 type mix-ups centered mainly in the V8 JavaScript engine. Alongside the security patches, the desktop update adds an option to quickly beam open tabs across hardware. Users signed in to the same Google account can right-click a tab and select Send to my device to push it to all or selected connected phones, tablets, or computers. [1][2]

While Chrome typically installs new releases automatically in the background, users can force the update through the About Google Chrome page under the browser settings menu. The patch lands during a fast-moving release cycle, with Chrome 158 scheduled to roll out in two weeks. [1]

Read the original reporting

2 outlets
PCWorld
[1] PCWorld

Chrome 157 fixes over 200 security flaws, 7 of them critical

Google just released Chrome 157.0.8103.38/39 for Windows and macOS and 157.0.8103.38 for Linux, fixing over 200 security vulnerabilities, some of which are critical. According to Google, none of the patched vulnerabilities have been exploited in the wild yet. Chrome 158 is due to be released in two weeks. What’s new in Chrome 157? In Chrome’s “What’s New” page that shows after updating, Google announces a new feature for sending open browser tabs to all (or select) devices.

via PCWorld
Read at PCWorld

Related coverage