Update Chrome Now: Google Fixes Its Eighth Zero-Day of 2026

Share

Google has patched another Chrome bug that attackers are already using. In its Stable channel update on Monday, November 9, Google says it is “aware that an exploit for CVE-2026-125350 exists in the wild.” The fix ships in Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux, along with 8 other security fixes.

Google Chrome logo
Image: Google
Key Takeaways: Chrome zero-day CVE-2026-125350
The bug: CVE-2026-125350, a High-severity use after free in Chrome’s XML code, reported anonymously on November 6.
Already exploited: Google confirms an exploit exists in the wild, but has not said who is behind it or who was targeted.
Eighth this year: security sites count it as the eighth exploited Chrome zero-day of 2026.
Version to get: Chrome 157.0.8103.50 or later on Windows, Mac and Linux. Extended Stable users need 156.0.8078.96.
Chromebooks: Google has not yet posted a ChromeOS Stable update that lists this fix. Keep an eye on About ChromeOS.

1. What happened

A quick turnaround: an anonymous researcher reported the flaw to Google on Friday, November 6. By Monday, Google had shipped the fix and confirmed that an exploit is being used in real attacks.

What a use after free means: the browser frees up a piece of memory but keeps a pointer to it. If an attacker can control what goes into that memory, a crafted web page can corrupt it and possibly run code. That is why bugs like this are rated High.

Details are limited on purpose: Google keeps bug reports private until most people have updated, so other attackers cannot copy the exploit. BleepingComputer and other security sites note this is the eighth Chrome zero-day exploited in attacks this year.

2. All 9 security fixes in this update

CVEAreaSeverity
CVE-2026-125350Use after free in XML (exploited in the wild)High
CVE-2026-125346Use after free in XMLHigh
CVE-2026-125345Uninitialized resource in WebGLHigh
CVE-2026-125347Incorrect authorization in FileSystemHigh
CVE-2026-125343Buffer overflow in CompositingHigh
CVE-2026-125348Out of bounds write in GPUHigh
CVE-2026-125344Type confusion in V8High
CVE-2026-125349Uninitialized resource in GPUMedium
CVE-2026-125342Uninitialized resource in GPUMedium
Breakdown of the 9 security fixes in Chrome 157.0.8103.50: 7 High and 2 Medium, with one High bug exploited in the wild
The 9 fixes in Chrome 157.0.8103.50 by severity. Only CVE-2026-125350 is known to be exploited. Data: Google. Graphic: ChromeGeek

Most were found by Google: Google’s own teams reported six of the nine bugs. The second XML bug, CVE-2026-125346, came from Arni Hardarson of Neonix Security, and one GPU bug came from Vo Duc Thang.

3. Which version you should have

PlatformVersion with the fixStatus
Chrome on Windows and Mac157.0.8103.50/.51Rolling out
Chrome on Linux157.0.8103.50Rolling out
Extended Stable (Windows and Mac)156.0.8078.96Rolling out
Chrome for Android157.0.8103.50, same security fixes as desktopRolling out
ChromeOS StableNo update listing this CVE posted yetNot yet

About Chromebooks: the latest ChromeOS Stable update, M-156 from November 6, does not list CVE-2026-125350, and Monday’s ChromeOS Beta note had no security details. We will update this post when Google posts a ChromeOS fix. In the meantime, keep your Chromebook updated and be careful with links from people you do not know.

4. How to update Chrome

  1. Open Chrome and click the three-dot menu in the top right.
  2. Go to Help, then About Google Chrome. Chrome checks for updates on its own.
  3. When it finishes downloading, click Relaunch. Your tabs come back after the restart.
  4. Check the version shows 157.0.8103.50 or later.
  5. On a Chromebook, open Settings, then About ChromeOS, and click Check for updates.

Using Edge, Brave, Opera or Vivaldi? these browsers are built on Chromium too, so install their next security update as soon as it arrives.

Our take

Eight exploited zero-days before the middle of November is a reminder that the browser is the main target on any computer. On Windows, Mac and Linux, this one takes a minute to fix, so do it now rather than waiting for Chrome to update on its own. Chromebook owners are in a waiting game until Google ships a ChromeOS build with the fix, and we will flag it as soon as it lands.


Discover more from Chrome Geek

Subscribe to get the latest posts sent to your email.

Sophie is a Chicago-based editor for Chrome Geek covering Chromebooks, Gemini, and the Google ecosystem. When she is offline, you can usually find her watching Blackhawks hockey or grabbing iced coffee in the city.