Security Digest · Nov 9, 2026 · Vulnerability · Browser

Chrome Zero-Day CVE-2026-125350: XML Use-After-Free

Exploited use-after-free in Chrome's XML code, fixed in 157.0.8103.50 on Nov 9. Relaunch now; Edge's fix was still pending on Nov 10.

Our verdict

Act now

Google says an exploit exists in the wild and the fix is only starting to roll out, so update and relaunch Chrome today and check whether your other Chromium browsers have a fix yet.

Who must act: Everyone running Chrome on Windows, macOS, Linux or Android below the fixed builds, and admins of fleets where updates are pinned, deferred or waiting on a relaunch.

Who can relax: Users already on Chrome 157.0.8103.50 or later, or Extended Stable 156.0.8078.96 or later, after a relaunch. Headless and server software that does not embed Chromium is not involved.

Affected
Google Chrome Stable before 157.0.8103.50
Google Chrome Extended Stable before 156.0.8078.96
Chrome for Android before 157.0.8103.50
Other Chromium-based browsers until their vendors ship the fix
Fixed in
Chrome 157.0.8103.50/.51 for Windows and Mac
Chrome 157.0.8103.50 for Linux
Chrome Extended Stable 156.0.8078.96 for Windows and Mac
Chrome 157.0.8103.50 for Android
Microsoft Edge: fix not released as of Nov 10, 2026
CVSS
Not scored
EPSS
1.9% (percentile 80)
CISA KEV
Yes, listed as known exploited
Exploitation
Exploited in the wild
Severity
High

What to do

  1. Open chrome://settings/help, let the update finish, and click Relaunch. The fix does not apply until the browser restarts.
  2. In managed fleets, report Chrome versions and flag every endpoint below 157.0.8103.50, or below 156.0.8078.96 on Extended Stable.
  3. Do not wait for the staged rollout on high-risk machines. Push the update through your management tool and force a relaunch with the RelaunchNotification policy.
  4. Watch Microsoft's Edge security release notes and deploy the Edge fix as soon as it ships.
  5. Check Brave, Opera, Vivaldi and any Electron or embedded Chromium apps for a release that includes this fix.

How to check if you are affected or compromised

  • Check the installed version: google-chrome --version on Linux, or chrome://version in the browser, and compare it with the fixed builds.
  • Google has published no indicators of compromise as of Nov 10, 2026. For high-risk users on old builds, review EDR for browser processes spawning unexpected executables and for new services, scheduled tasks or launch agents.

What happened#

On November 9, 2026, Google released Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux, with nine security fixes. One of them is CVE-2026-125350, a high-severity use-after-free in Chrome's XML code. Google's note is one sentence long: "Google is aware that an exploit for CVE-2026-125350 exists in the wild."

An anonymous researcher reported the bug on November 6, so the fix shipped three days later. Google has kept the bug details restricted, which is its normal practice until most users have updated. It has not said who is using the exploit, against whom, or whether a second bug is needed to escape Chrome's sandbox. According to BleepingComputer and The Hacker News, this is the eighth exploited Chrome zero-day of 2026.

As of November 10, CVE-2026-125350 had no published CVE.org or NVD record and no CVSS score, and it was not in CISA's KEV catalog (version 2026.11.09). The same update also fixes CVE-2026-125346, a separate use-after-free in XML. Google does not say that one is exploited.

Who is affected#

Anyone running Chrome below the fixed builds. The Extended Stable channel gets the fix in 156.0.8078.96 for Windows and Mac. Chrome for Android 157.0.8103.50 carries the same security fixes as desktop and reaches Google Play over a few days.

Other Chromium-based browsers need their own updates. Microsoft's Edge release notes say, in an entry dated November 9, "Microsoft is aware of the recent exploits existing in the wild. We are actively working on releasing a security fix." The entry does not name this CVE or give a version, and Edge's latest Stable build at the time, 157.0.4341.42, dates from November 5.

Do you really need to act?#

Yes, and it takes about a minute. Chrome is one of the most widely deployed applications in any company, an exploit exists, and the usual delivery route for a browser bug is a web page or a malicious ad. The honest limits are that Google has described no campaign, past Chrome zero-days have often been used in targeted attacks, and most people may never be aimed at. That does not change the advice, because updating costs almost nothing.

The catch is timing. Google says the release "will roll out over the coming days/weeks," and a downloaded update does nothing until the browser restarts. Machines that stay open for weeks are the ones that stay exposed. Edge users have no fix to apply yet, so high-risk Edge users may want to use an updated Chrome for untrusted browsing until Microsoft ships one.

What to do now#

  1. Open chrome://settings/help, wait for the update, and click Relaunch.
  2. Confirm the version. On Linux, run google-chrome --version. On macOS, run "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --version. Anywhere, open chrome://version.
  3. For managed fleets, report versions from your endpoint tool and flag anything below 157.0.8103.50, or below 156.0.8078.96 on Extended Stable. Use the RelaunchNotification policy so updates actually apply.
  4. Check for policies that pin Chrome to an old version or defer updates, and lift them for this release.
  5. Deploy the Edge fix when Microsoft publishes it, and check Brave, Opera, Vivaldi and any Electron or embedded Chromium apps for updates.

How to tell if you were hit#

You probably cannot tell from the browser. Google has published no indicators of compromise as of November 10, and renderer exploits leave little on disk. Start by listing machines that ran a build below the fix, then concentrate on high-risk users such as administrators, executives and people with production access. Look in EDR for browser processes starting shells or unfamiliar executables, and for new services, scheduled tasks or launch agents created around browsing sessions.

Timeline#

  • — Microsoft ships Edge Stable 157.0.4341.42, before Chrome's fix.
  • — An anonymous researcher reports CVE-2026-125350 to Google.
  • — Google ships the fix in Stable and Extended Stable, says an exploit exists in the wild, and releases Chrome for Android 157.0.8103.50. Microsoft says it is working on an Edge fix.
  • — No CVE.org record, CVSS score or KEV listing yet.

Vulnerability records

  • CVE-2026-125350 · KEV 2026-11-10 · Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. Google Chrome Releases — Stable Channel Update for Desktop (Nov 9, 2026) chromereleases.googleblog.com
  2. Google Chrome Releases — Extended Stable Update for Desktop (Nov 9, 2026) chromereleases.googleblog.com
  3. Google Chrome Releases — Chrome for Android Update (Nov 9, 2026) chromereleases.googleblog.com
  4. Microsoft — Release notes for Microsoft Edge Security Updates learn.microsoft.com

Coverage and analysis

  1. BleepingComputer — Google patches eighth Chrome zero-day exploited in attacks this year bleepingcomputer.com
  2. The Hacker News — Google Issues Chrome Security Update for Eighth Actively Exploited Zero-Day of 2026 thehackernews.com