techcoff.com

Chrome Zero-Day CVE-2026-125350: Update Chrome Now (2-Minute Fix)

Chrome Zero-Day CVE-2026-125350: Update Chrome Now (2-Minute Fix)

Yes — update Chrome right now. Google confirmed on November 9, 2026 that attackers are already exploiting a flaw in Chrome, CVE-2026-125350, and the fix takes about two minutes: open chrome://settings/help, let Chrome update, and relaunch.

Version 157.0.8103.78 or later on Windows or Mac (157.0.8103.78 on Linux) means you are already safe. Anything older is not — just visiting a booby-trapped webpage is enough to trigger it. No download, no password, no click on a shady button required.

Key takeaway: this is not a “patch it later” update — it is an actively exploited zero-day, the eighth attacked in the wild this year, and the fix is already waiting in your browser. Two minutes now beats a hacked browser later.

What Is CVE-2026-125350? (Plain English)

A “zero-day” is a flaw hackers found and used before Google knew about it — zero days of warning. CVE-2026-125350 is a use-after-free bug in Chrome’s XML code (XSLT webpages): Chrome frees a chunk of memory, then accidentally keeps using it, and a crafted webpage can hijack that mistake to run malicious code inside Chrome’s sandbox.

The flaw scores 8.8 out of 10 (High) on the CVE record — Google itself published no score. Reported anonymously on November 6, 2026, it was fixed three days later, with Google confirming an exploit already exists in the wild.

On November 10, the US cybersecurity agency CISA added it to its Known Exploited Vulnerabilities catalog, with a November 24, 2026 patch deadline for federal agencies — the government’s way of saying this one is real and already being used.

Key takeaway: you don’t need to understand XML or memory bugs — just this: the attack works through an ordinary webpage, and the patch is already out.

Am I Affected? Check Your Chrome Version in 30 Seconds

If you use Chrome on Windows, Mac, Linux, or Android, assume you are affected until you check:

  • On desktop: type chrome://settings/help in the address bar and press Enter. Chrome shows your version number — and starts checking for an update automatically.
  • On Android: open the Play Store, tap your profile icon, then Manage apps & device, and look for a Chrome update.

If your number is equal to or higher than the safe version below, you are protected. If it is lower, update now using the next section.

PlatformSafe version (or later)Released
Windows157.0.8103.78 / .79November 11, 2026
Mac157.0.8103.78 / .79November 11, 2026
Linux157.0.8103.78November 11, 2026
Android157.0.8103.50 or later (via Play Store)November 2026
Extended Stable (work PCs)156.0.8078.96November 9, 2026

Google shipped the first emergency fix on November 9 (157.0.8103.50/.51), then a fuller Stable update on November 11 (157.0.8103.78/.79). Aim for the November 11 build — it includes the zero-day fix plus extra security and stability fixes. Emergency patches get weaponized fast — see our PHP critical vulnerability guide for the same pattern in October.

How to Update Google Chrome to the Latest Version (2026)

Chrome usually updates itself in the background, but only finishes when you relaunch. If you have not restarted Chrome in days, the patch may already be waiting. Here is how to finish it on every platform.

Update Chrome on Windows

  • Open Chrome and click the three dots in the top-right corner.
  • Go to Help > About Google Chrome (or type chrome://settings/help).
  • Chrome checks for updates automatically and installs any it finds.
  • Click Relaunch when it appears. Your tabs reopen automatically.

Update Chrome on Mac

  • Same steps as Windows: three dots > Help > About Google Chrome, then Relaunch.
  • If the three-dot menu shows a colored arrow, an update has been waiting — red means it has waited more than a week. Relaunch immediately.

Update Chrome on Linux

  • Open Chrome and go to Help > About Google Chrome (chrome://settings/help).
  • If an update is available, Chrome downloads it — then relaunch.
  • If nothing appears, update through your package manager instead — on Ubuntu/Debian, run sudo apt update && sudo apt upgrade google-chrome-stable, then relaunch Chrome.

Update Chrome on Android

  • Open the Play Store and tap your profile icon.
  • Tap Manage apps & device, then Updates available — find Chrome and tap Update. If Chrome is not listed, you are already on the latest version.
  • Check your version in Chrome: three dots > Settings > About Chrome.

Key takeaway: the update itself is not the finish line — the relaunch is. Chrome cannot apply the patch while the old version is running, so always click Relaunch, even with 40 tabs open. They will come back.

What Happens If You Don’t Update?

Picture this: a link in a WhatsApp message, or a Google result for a product review. The page loads and looks completely normal — no download prompt, no warning. Behind the scenes, that page’s XML code triggers the flaw, and malicious code starts running inside your browser.

That is the real danger of a drive-by zero-day: nothing to spot, nothing to click. A compromised ad on a legitimate news site, a hacked small-business page, or a link in a group chat can all carry the attack. Once code runs inside Chrome, attackers can steal saved passwords, session cookies, and banking logins.

This is not hypothetical — Google confirmed the exploit exists in the wild, so real attackers are already using it. Every day on an old version keeps you on the easy-target list. Use-after-free flaws are a classic way in — see our OWASP Top 10 vulnerabilities explained for why memory bugs keep topping the charts.

Do Edge, Brave and Opera Need Updating Too?

Yes. Edge, Brave, Opera, and Vivaldi are all built on Chromium — the same engine as Chrome — so they share the vulnerable XML code, and CISA specifically warned they may also be affected.

Each browser ships its own fix, so updating Chrome does not update Edge. Open your other browser’s About page (edge://settings/help for Edge, brave://settings/help for Brave) and install the update — even one you rarely open needs its own patch.

Key takeaway: one patch does not cover every browser on your computer. If it is built on Chromium, it needs its own update.

After the Update: 3 Quick Checks

Updating takes two minutes. These three checks take one more:

  • Verify the version number. Go back to chrome://settings/help and confirm it matches the safe version above. If it still shows an old number, relaunch Chrome again.
  • Keep automatic updates on. Chrome updates itself by default — but if you disabled them, or your work laptop is managed by IT, check with your admin. A browser that cannot update itself will fall behind again.
  • Review your saved passwords. If you were on an old version for a while, run the built-in checkup at chrome://settings/passwords for leaked credentials, and change any banking or email password you entered while unpatched. The same “verify, then harden” routine in our WordPress security audit checklist works for your browser too.

Frequently Asked Questions

What is a zero-day vulnerability?

A zero-day is a flaw attackers discover and exploit before the software maker knows it exists. By the time the patch ships, attacks may already be underway — as they were here.

Is my Chrome version safe?

Open chrome://settings/help. You are safe on 157.0.8103.78 or later (Windows/Mac), 157.0.8103.78 (Linux), or 157.0.8103.50 or later (Android). Anything lower needs an update and a relaunch right now.

What happens if I don’t update Chrome?

You stay vulnerable to a confirmed, actively exploited flaw. Visiting a malicious or compromised webpage could let attackers run code in your browser and steal passwords, cookies, and sessions — with no download or suspicious click needed.

Does Microsoft Edge need updating too?

Yes. Edge, Brave, Opera, and Vivaldi are Chromium-based and share the vulnerable code, so each needs its own update — open its About page (for Edge: edge://settings/help) and install the latest version.

Chrome says “up to date” but my version looks old — what now?

First, relaunch Chrome — the update may be downloaded but waiting for a restart. If the version is still old, your browser may be managed by your employer (check with IT) or auto-updates may be off. On Linux, use your package manager instead.

Can this flaw affect my Android phone?

Yes — Android builds before 157.0.8103.50 are listed as affected. Update Chrome from the Play Store like any app, and keep auto-updates on so the next emergency patch lands without you thinking about it.

The Bottom Line

Google fixed CVE-2026-125350 in three days — but a fix only protects the people who install it. Attackers already have a working exploit, the flaw needs nothing more than a visit to a bad webpage, and it is the eighth Chrome zero-day exploited this year.

So do it now: open chrome://settings/help, let the update land, click Relaunch, and check the version number. Two minutes, and your browser stops being an easy target.

Leave a Comment