Chrome 157 Patches Eighth Exploited Zero-Day of 2026
By @sharedot · · 6 pages
- Cybersecurity
- Chrome
- Zero Day
- Browser Security
Google's Chrome 157 update fixes nine flaws, including CVE-2026-125350, a use-after-free XML zero-day exploited in the wild.
What happened: an actively exploited XML bug
Google on Monday informed Chrome users of new security updates that patch nine vulnerabilities, including one exploited in the wild. The flaw, tracked as CVE-2026-125350 and rated high severity, is a use-after-free bug in the browser's XML component.
An anonymous security researcher reported the issue to Google on November 6, 2026. Google acknowledged it is "aware that an exploit for CVE-2026-125350 exists in the wild," but has not shared details on the attacks or who is behind them.
Why it matters: the eighth zero-day this year
This is the eighth Chrome zero-day exploited in the wild in 2026, following CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046 and CVE-2026-87491.
Use-after-free bugs occur when a program accesses memory after it has been freed, potentially enabling data corruption, crashes, or arbitrary code execution.
Google has kept bug details restricted until a majority of users are updated, and CISA has yet to add the flaw to its Known Exploited Vulnerabilities catalog.
What else is patched and who is affected
Beyond the zero-day, the Chrome 157 updates fix six high-severity vulnerabilities in the WebGL, FileSystem, Compositing, GPU, V8 and XML components, most of which Google discovered internally. Two medium-severity uninitialized resource issues in the GPU component were also fixed.
The fixes arrive in versions 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux. Users of Chromium-based browsers such as Microsoft Edge, Brave, Opera and Vivaldi are advised to apply the fixes when available.
What comes next
Users can protect themselves by navigating to More > Help > About Google Chrome and selecting Relaunch to confirm version 157.0.8103.50 or later is installed.
Google notes that access to bug details may remain restricted if the bug exists in a third-party library that other projects depend on but have not yet fixed. With no information available on the in-the-wild attacks, defenders should treat the flaw as actively targeted and patch promptly.