Google released Chrome 157.0.8103.50/.51 for Windows and macOS and 157.0.8103.50 for Linux on 9 November. The update contains nine security fixes. Google says an exploit for one of them, CVE-2026-125350, exists in the wild.
This is a browser security update, not a reported malicious-extension incident. The practical priority is to confirm that managed devices receive the stable update as it rolls out, rather than assuming that a browser restart or an extension review alone has removed the risk.
Checks for managed browser estates
- Confirm the Chrome version deployed across managed Windows, macOS and Linux devices.
- Check whether browser-update policies or deferred rings could leave devices on an earlier build.
- Ask users to relaunch Chrome where an update has downloaded but not completed.
- Treat unexplained browser crashes or suspicious activity as an investigation prompt; Google has not published exploit details while users are updating.
- Continue reviewing installed extensions, permissions and publisher changes separately: this Chrome vulnerability notice does not establish that an extension caused the issue.
Google lists seven high-severity fixes and two medium-severity fixes in the release. Its advisory says details may remain restricted until most users have received the update.
For organisations managing browser and extension risk together, MobSTR’s browser extension risk management overview explains how permission, publisher and change evidence can support ongoing review. Book a demo to discuss application and extension oversight.
Source
Google Chrome Releases — Stable Channel Update for Desktop, 9 November 2026