Google released Chrome 157 for desktop on 9 November with nine security fixes, and says it is aware that an exploit for one of them, CVE-2026-125350, exists in the wild.
The Stable channel moved to 157.0.8103.50 and .51 for Windows and Mac and 157.0.8103.50 for Linux, rolling out over the coming days and weeks. Google’s release note rates CVE-2026-125350 High, describes it as a use after free in XML, and credits an anonymous reporter, with the report dated 6 November. The note states: “Google is aware that an exploit for CVE-2026-125350 exists in the wild.” It does not say who is exploiting the flaw or against whom, and it keeps bug details restricted until most users have updated.
Seven of the nine fixes are rated High and two Medium. Besides the exploited flaw, the High-rated list includes a second use after free in XML, CVE-2026-125346, reported by Arni Hardarson of Neonix Security on 12 October, plus flaws in WebGL, FileSystem, Compositing, GPU and V8, most credited to Google’s own reporters. Chrome for Android 157.0.8103.50 carries the same security fixes as the desktop build, according to Google.
The practical issue is the gap between release and rollout. Google says the build reaches users over days or weeks, so a managed fleet that waits for the automatic push can run the vulnerable build while an exploit is known to exist. In our reading, a flaw with confirmed in-the-wild use belongs in the same fast patch lane as the entries we covered when CISA added a WordPress core flaw and when two Ivanti Connect Secure zero-days reached the exploited list.
Defenders should confirm that managed endpoints report version 157.0.8103.50 or later, trigger the update through their management tooling instead of waiting for the rollout, and relaunch the browser, since the fix applies only after a restart. Teams running other Chromium-based browsers should watch for those vendors’ own releases.
Source: Chrome Releases, Stable Channel Update for Desktop, 9 November 2026