browsers.to

Chrome's eighth exploited zero-day of 2026 is patched: update now

Attackers were already using a flaw in how Chrome handles XML when Google shipped the fix on 9 November. Brave and Vivaldi have updated too; check your Chromium browser.

The Tab Report

2 min read

The short version

What happened
Google patched CVE-2026-125350, a Chrome bug that attackers were already exploiting, on 9 November, the eighth such Chrome flaw of 2026.
Who's affected
Anyone on Chrome before 157.0.8103.50, and users of other Chromium-based browsers until their maker ships the fix.
What to do
Open Chrome's About page, let it update and relaunch. Brave and Vivaldi have shipped fixes; check Edge, Opera and others.

Google has fixed a Chrome security flaw that attackers were already using against real people. The update shipped on 9 November, and it is the eighth Chrome bug exploited in attacks that Google has had to patch this year. If you haven't restarted Chrome since 9 November, do it now.

What happened

Google's Chrome Releases blog lists the fix for CVE-2026-125350 in the stable update that moved Chrome to 157.0.8103.50 (Windows and Mac get 157.0.8103.50 or .51, Linux gets .50). Google's notice says it "is aware that an exploit for CVE-2026-125350 exists in the wild", and the Extended Stable channel, a slower-moving version of Chrome, also carries the fix.

BleepingComputer and Malwarebytes both describe the flaw as a high-severity use-after-free in Chrome's XML handling, a memory error where a program keeps using data it has already released. Malwarebytes reports Google was told about it by an unnamed third party on 6 November, three days before the fix. Google hasn't shared details about who is being attacked or how.

The US cyber agency CISA added the bug to its Known Exploited Vulnerabilities catalogue on 10 November, which is the list government agencies must patch against by a deadline (24 November here).

Why it matters

Use-after-free bugs in browsers are often used to run an attacker's code when you visit a booby-trapped page, though Google hasn't said how this one is being used. Either way, an "exploit in the wild" label means the fix shouldn't wait for your next scheduled restart.

The update contains nine security fixes in total, according to Malwarebytes, but this is the one being used in attacks. By BleepingComputer's count, it is the eighth exploited Chrome flaw this year.

Who is affected

Chrome on Windows, macOS, Linux and Android. Chrome's engine, Chromium, powers many other browsers, so they need the same fix:

  • Brave shipped version 1.99.56 on 10 November, which its release notes say upgrades Chromium to 157.0.8103.50.
  • Vivaldi released a minor update to Desktop 8.3 the same day, moving to Chromium 156 with the security fixes and listing this CVE.
  • We couldn't confirm the current status for Microsoft Edge or Opera from their release notes at the time of writing, so check them yourself.

What to do

  1. In Chrome, open the three-dot menu, then Help → About Google Chrome. It checks for the update and downloads it.
  2. Click Relaunch. The fix only applies after a restart.
  3. On Android, update Chrome from Google Play.
  4. On other Chromium browsers, open their About or update page and install anything pending.

To compare how the major browsers handle updates and security, see Chrome vs Firefox.

Sources (6)

  1. 1.Chrome Releases (Google): November 2026 stable, extended stable and Android updates · 9 November 2026
  2. 2.BleepingComputer: Google patches eighth Chrome zero-day exploited in attacks this year · 10 November 2026
  3. 3.Malwarebytes: Update Chrome now to fix a flaw attackers are exploiting · 10 November 2026
  4. 4.CISA: Known Exploited Vulnerabilities Catalog · 10 November 2026
  5. 5.Brave: brave-browser release notes · 10 November 2026
  6. 6.Vivaldi: Desktop blog, minor update for 8.3 · 10 November 2026