Skip to content

Chrome Zero-Day CVE-2026-125350: How to Update Chrome Now

By Bikram Bhujel

Google fixed another Chrome zero-day on 9 November, and this one is already being used in attacks. It's the eighth Chrome zero-day exploited this year. Chrome updates itself, but only after you restart it, and plenty of people keep the same Chrome window open for weeks.

So this post is the practical bit: how to check your Chrome version on each device, how to force the update, how to handle Edge and Brave (which use the same engine), and how to update lots of PCs at once if you look after an office.


About Google Chrome page showing Chrome updated to version 157.0.8103.51 to fix the CVE-2026-125350 zero-day

Quick answer

CVE-2026-125350 is a use-after-free bug in Chrome's XML component, and Google says an exploit for it exists in the wild. It's fixed in Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux, released on 9 November 2026. To update, open chrome://settings/help, let it download, then click Relaunch. The fix doesn't apply until Chrome restarts. Edge, Brave, Opera and Vivaldi use the same Chromium engine but ship fixes on their own schedule, so update those separately.

What the bug is, in plain words

A use-after-free is a memory bug: the program frees a piece of memory, but something still points at it and uses it later. An attacker who can control what ends up in that memory can sometimes make the program run their code. In this case the bug is in the part of Chrome that parses XML, and a specially crafted web page is enough to trigger it.

Google's Chrome Releases post for 9 November says it's "aware that an exploit for CVE-2026-125350 exists in the wild", which is Google's usual wording when a bug is being used in real attacks. As usual, it hasn't said who's using it or against whom. BleepingComputer counts it as the eighth exploited Chrome zero-day of 2026.

The same update fixes nine security issues in total, so it's worth installing even if you think nobody would target you.

Which version you need

PlatformFixed version (or later)
Windows157.0.8103.50 or .51
Mac157.0.8103.50 or .51
Linux157.0.8103.50
AndroidLatest version from the Play Store

Anything starting with 157.0.8103.50 or higher is fine. If you see 156 or an older 157 build, you're not patched.

Step 1: Update Chrome on Windows, Mac or Linux

  1. Open Chrome and type chrome://settings/help in the address bar. (Or: three-dot menu > Help > About Google Chrome.)
  2. Chrome checks for updates and downloads the new version.
  3. Click Relaunch.
  4. Open the same page again and confirm the version.

Relaunching restores your open tabs, so you won't lose anything except unsaved form text. Save that first.

The step people skip is the relaunch. Chrome can download an update and sit there with it for days, with the old, vulnerable version still running. If the three-dot menu shows a coloured "Update" or a small arrow, that's what it's waiting for.

Checking the version from the command line

Useful if you're checking someone else's PC remotely, or a few at once. On Windows, in PowerShell:

(Get-Item "C:\Program Files\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion

On Linux:

google-chrome --version

On Linux, Chrome updates through your package manager, not by itself. On Ubuntu or Debian with Google's repository:

sudo apt update
sudo apt install --only-upgrade google-chrome-stable

Step 2: Update Chrome on your phone

  • Android: open the Play Store, tap your profile picture, then Manage apps & device, and update Chrome. Close and reopen it afterwards.
  • iPhone and iPad: update Chrome from the App Store. On iOS, Chrome runs on Apple's WebKit engine rather than Google's, so desktop Chrome bugs often don't apply in the same way. Update anyway, it costs nothing.

Step 3: Don't forget Edge, Brave and the others

Microsoft Edge, Brave, Opera and Vivaldi are all built on Chromium, the same engine as Chrome. A bug in Chromium's XML code is usually a bug in all of them. Each company ships its own update, though, and not always on the same day as Google.

BrowserWhere to check and update
Microsoft Edgeedge://settings/help
Bravebrave://settings/help
Operaopera://update
VivaldiVivaldi menu > Help > Check for Updates

If one of them says it's up to date but its release notes don't mention CVE-2026-125350 yet, check again in a day or two.

Step 4: Updating a whole office

If you look after more than a handful of PCs, don't walk around clicking "Relaunch". A few options, depending on what you already have:

  • winget (built into Windows 10 and 11). From an admin terminal on each PC, or pushed through a script:
winget upgrade --id Google.Chrome --silent --accept-package-agreements --accept-source-agreements
  • Group Policy or Intune with Chrome's policy templates. The RelaunchNotification and RelaunchNotificationPeriod policies make Chrome nag users to restart, and can force the restart after the time you set. This is the setting that actually closes the gap, because the download part already happens on its own.
  • Check the result. Run the PowerShell version check above across your machines, or look at the browser report in Chrome Browser Cloud Management if you use it.

Whatever you use, tell people before forcing a relaunch. A browser that vanishes mid-way through an online form makes nobody like IT.

What can go wrong

  • "Updates are disabled by your administrator". On a work PC, that's deliberate. Tell your IT team about this update rather than trying to get around it.
  • Chrome says up to date but shows 156. Some managed PCs are on the Extended Stable channel, which runs one version behind and gets security fixes separately. Check with whoever manages the PC.
  • Chrome was installed per-user. If Chrome lives under AppData rather than Program Files, the PowerShell check above won't find it. Check chrome://settings/help in that user's account instead.

How to roll back (and why you shouldn't)

Google doesn't offer a simple downgrade, and going back to a version with a known, actively exploited bug is a bad trade. If the update breaks a website or an internal web app, report it, use another updated browser for that one site in the meantime, and keep Chrome patched.

A few things I learned

  • Downloaded isn't installed. Chrome's update only takes effect after a relaunch. That one click is the whole job.
  • One engine, many browsers. Patching Chrome and forgetting Edge leaves the same hole open on the same PC.
  • Force relaunches in an office. The relaunch policy is the difference between "patched in a day" and "patched whenever someone reboots".

If you're choosing a browser anyway, I compared the best privacy browsers in 2026 and looked at Brave Origin separately. For other urgent patches this month, see my posts on the exploited WordPress flaw and the Fortinet fixes. If you need patching handled across an office, that's part of my IT services.

Frequently asked questions

What is CVE-2026-125350?

It is a high-severity use-after-free bug in Google Chrome's XML component. A crafted web page can trigger it, and Google says an exploit exists in the wild. It is fixed in Chrome 157.0.8103.50 and later, released on 9 November 2026.

How do I know if my Chrome is updated?

Type chrome://settings/help in the address bar. If the version starts with 157.0.8103.50 or higher, you are patched. If Chrome shows a Relaunch button, click it, because the fix only applies after Chrome restarts.

Is Microsoft Edge affected by the Chrome zero-day?

Edge is built on Chromium, the same engine as Chrome, so Chromium bugs usually affect it too. Microsoft ships its own fix on its own schedule. Check edge://settings/help and install any update, and do the same for Brave, Opera and Vivaldi.

Do I need to update Chrome on my phone?

Yes. On Android, update Chrome from the Play Store. On iPhone, update it from the App Store. iOS Chrome uses Apple's WebKit engine, so desktop bugs may not apply the same way, but updating costs nothing.

How do I force Chrome to update on all office PCs?

Use winget upgrade for Google.Chrome through a script, or set the RelaunchNotification and RelaunchNotificationPeriod policies with Group Policy or Intune so Chrome restarts after a set time. Then check versions across machines to confirm.

Comments

Questions and corrections are welcome. I read every comment before it appears, and remove spam and promotional links.