Skip to main content
Season 3 ends in 25 d 11:42:37 $2,000 10,000 pts = 1 month Premium
Online Security

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

Published 11 min read
Open the post and read it to claim 30 points
A laptop with a blank browser window and a gold update progress bar, illustrating the Chrome zero-day CVE-2026-125350 update

Sign in and earn +30 points by reading this

Read to the end, wait a few seconds, then tap the claim button below.

In short

Chrome zero-day CVE-2026-125350, a use-after-free bug in Chrome's XML handling, is being exploited in attacks, Google said on 9 November 2026 [1]. The fix is Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux; update and relaunch the browser now [1][2]. CISA added it to its exploited-vulnerabilities list on 10 November [3].

Key takeaways

  1. Google says an exploit for CVE-2026-125350 exists in the wild; it is rated High severity [1].
  2. Fixed versions: 157.0.8103.50/.51 on Windows and Mac, 157.0.8103.50 on Linux, released 9 November 2026 [1].
  3. The update fixes 9 security issues in total, including WebGL, GPU and V8 bugs [1].
  4. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 10 November 2026 [3].
  5. Chromium-based browsers share the bug: Microsoft shipped a fix in Edge for Android on 11 November and said it was working on a fix for the exploit [4].
  6. Chrome updates only apply after you relaunch the browser [5].
On this page 13 sections
  1. What is the Chrome zero-day CVE-2026-125350?
  2. What can attackers do with a use-after-free bug?
  3. How do I update Chrome right now?
  4. Which versions fix the Chrome zero-day?
  5. Are Edge, Brave and other browsers affected?
  6. Why did CISA add it to the KEV catalog?
  7. What else should you do to stay safe?
  8. How should companies roll out the Chrome fix?
  9. When was the Chrome zero-day reported and fixed?
  10. Common mistakes
  11. Frequently asked questions
  12. Glossary
  13. Sources

What is the Chrome zero-day CVE-2026-125350?

CVE-2026-125350 is a high-severity "use after free" vulnerability in the XML component of Google Chrome, and Google states that "an exploit for CVE-2026-125350 exists in the wild" [1]. A zero-day is a flaw that attackers use before, or at the same time as, the vendor ships a fix.

Google's Stable Channel Update for Desktop, published on Monday 9 November 2026, lists two reports for it: Arni Hardarson of Neonix Security on 12 October 2026 and an anonymous researcher on 6 November 2026 [1]. Google's note says access to bug details "may be kept restricted until a majority of users are updated with a fix" [1], and BleepingComputer reports that Google has not shared further details about the attacks [6]. So there is no public information yet on who used the exploit or against whom.

BleepingComputer reported it as the eighth Chrome zero-day exploited in attacks in 2026 [6]. NHS England's cyber security operations centre rated the threat medium and assessed further exploitation as likely [2].

What can attackers do with a use-after-free bug?

A use-after-free happens when a program keeps using a piece of memory after it has released it; an attacker who controls what fills that memory can sometimes make the program run their code [6]. In a browser, the usual route is a specially crafted web page: you visit it, and the page triggers the bug.

Google has not published the attack details for this case [1][6]. The official CVE entry says the flaw allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page [7], and CISA's catalog entry gives the same description [8]. Code that runs only inside the sandbox is restricted; Google has not said whether the exploit was combined with any other flaw. Because the trigger is a web page, updating quickly matters even if you only visit sites you know.

Google's post names no workaround, only the updated version [1], so installing the update and relaunching is the protection to rely on.

A row of glowing memory blocks with one freed block being refilled by a dark red shape, explaining a use-after-free bug in Chrome
A use-after-free lets attacker-controlled data take the place of memory the browser has already released.

How do I update Chrome right now?

Open Chrome, go to the three-dot menu, choose Help and then About Google Chrome, let it check, and click Relaunch [5]. Google's help page explains that updates normally install in the background but only take effect when you close and reopen the browser [5].

  1. Windows and Mac: More (three dots) > Help > About Google Chrome. Wait for the check, then click Relaunch. If there is no Relaunch button, you are on the latest version [5].
  2. Confirm the number: the version under the Google Chrome heading should be 157.0.8103.50 or .51 (Windows, Mac) or 157.0.8103.50 (Linux) or later [1].
  3. Linux: update through your package manager [5].
  4. Chromebook: update the ChromeOS system itself; Chrome updates with it [5].

Your open tabs come back after the relaunch, but Incognito windows do not [5]. Google said the update "will roll out over the coming days/weeks" [1], so if About Google Chrome does not offer it yet, check again later the same day.

A laptop screen with a large glowing gold blank button, a mouse cursor on it and a refresh arrow beside it
Chrome installs updates in the background but only applies them when you relaunch.

Which versions fix the Chrome zero-day?

Chrome 157.0.8103.50/.51 for Windows and Mac and 157.0.8103.50 for Linux fix the flaw; any earlier version is affected [1][2]. NHS England lists the affected platforms as Chrome for Windows, macOS and Linux before those versions [2].

Besides CVE-2026-125350, the post lists seven other CVEs [1]. Five are high severity and were reported by Google: an uninitialized resource in WebGL (CVE-2026-125345), incorrect authorization in FileSystem (CVE-2026-125347), a buffer overflow in Compositing (CVE-2026-125343), an out-of-bounds write in GPU (CVE-2026-125348) and a type confusion in the V8 JavaScript engine (CVE-2026-125344) [1]. Two medium-severity GPU issues are also listed [1]. Google says the update includes nine security fixes but lists only eight CVE entries, and only CVE-2026-125350 is marked as exploited [1].

Are Edge, Brave and other browsers affected?

Browsers built on Chromium share Chrome's code, so they need their own patched release; CISA lists the bug as a "Google Chromium" vulnerability and says other Chromium-based browsers, such as Microsoft Edge and Opera, may also be affected [3][8].

Microsoft's Edge security release notes show two steps. On 9 November 2026 Microsoft wrote that it was aware of exploits in the wild and was "actively working on releasing a security fix" [4]. On 11 November it released Edge for Android version 157.0.4341.53, which it said contains the fix for CVE-2026-125350 [4]. When the notes were checked on 13 November 2026, they did not yet list a desktop Edge build with the fix [4]. Desktop Edge users should check edge://settings/help for updates and apply any new version as soon as it appears.

For Brave, Opera, Vivaldi and other Chromium browsers, look for a release based on Chromium 157.0.8103.50 or later in the vendor's release notes, and relaunch after updating. Firefox and Safari are not Chromium browsers, and none of the sources used here lists them as affected.

Four blank browser windows joined by glowing cables to one blue crystal core, one marked with a gold shield
Chromium-based browsers share the same code, so each needs its own patched release.

Why did CISA add it to the KEV catalog?

CISA adds a vulnerability to its Known Exploited Vulnerabilities (KEV) catalog when there is evidence of active exploitation; it added CVE-2026-125350 on 10 November 2026 together with five other flaws [3]. The same batch included CVE-2026-124194, a Microsoft Outlook flaw, and two Barracuda vulnerabilities [3].

The listing matters most for US federal civilian agencies: under Binding Operational Directive 26-04 they must prioritise rapid remediation of high-risk KEV vulnerabilities on publicly exposed assets that give total control after exploitation, while CISA encourages all organisations to prioritise KEV entries too [3]. For a company, a KEV listing is a strong signal to push the browser update through management tools rather than wait for users to relaunch.

What else should you do to stay safe?

Update, relaunch, then reduce the chance of landing on a malicious page [1][5].

  • Restart the browser when it shows a pending update, because updates apply only after a relaunch [5].
  • Remove extensions you do not use.
  • Be careful with links in unexpected messages, which are a common way to deliver exploit pages. The Pouyam guide What Is Phishing? How to Recognise Fake Emails, Texts and QR Codes shows the signs.
  • Use a password manager and two-factor sign-in, so a compromised browser session is less damaging; see Password Managers Explained: How They Work and Whether They Are Safe.
  • For background on why so many new CVEs appear, read AI That Finds Security Bugs: What Glasswing and New CVEs Mean for You.

How should companies roll out the Chrome fix?

Treat CVE-2026-125350 as an emergency change: push Chrome 157.0.8103.50/.51 or later to all managed devices and force a relaunch within a short deadline [1][3]. CISA's KEV listing is a strong reason for that priority, and NHS England advised affected organisations to apply the updates "as soon as possible" [3][2].

  1. Inventory: list every Chromium-based browser on your fleet, including Edge, embedded browsers in apps, and kiosk devices, because CISA describes the flaw as a Chromium bug, not only a Chrome bug [3]. CISA's catalog entry says a crafted webpage can let a remote attacker run code inside the browser sandbox, and it lists 24 November 2026 as the due date for US federal agencies [8].
  2. Deploy: use your management tool's update policy to install the new version, then set a relaunch notification with a deadline, since updates take effect only after restart [5].
  3. Verify: report on installed versions after 24 to 48 hours and chase devices still below 157.0.8103.50 [1].
  4. Edge desktop: watch Microsoft's security release notes and deploy the fixed build on the day it appears [4].
  5. Monitor: Google's post lists no indicators of compromise, so watch for unusual browser child processes or unexpected downloads rather than a specific signature [1].

Home users do not need any of this: updating and relaunching is enough [5].

When was the Chrome zero-day reported and fixed?

Google's post lists a report dated 12 October 2026 and a second, anonymous report dated 6 November; the fix shipped on 9 November [1]. NHS England published its alert on 10 November at 4:04 p.m., and CISA added the bug to the KEV catalog the same day [2][3]. Microsoft fixed Edge for Android on 11 November [4].

Google has not said which report, if either, relates to the exploitation, nor named any target [1][6]. Until it does, any claim about who was attacked is speculation.

Security fixes in Chrome 157.0.8103.50/.51 (Google, 9 November 2026)
CVESeverityComponent and bug typeExploited?
CVE-2026-125350HighXML: use after freeYes, exploit in the wild
CVE-2026-125345HighWebGL: uninitialized resourceNot stated
CVE-2026-125347HighFileSystem: incorrect authorizationNot stated
CVE-2026-125343HighCompositing: buffer overflowNot stated
CVE-2026-125348HighGPU: out of bounds writeNot stated
CVE-2026-125344HighV8: type confusionNot stated
CVE-2026-125349MediumGPU: uninitialized resourceNot stated
CVE-2026-125342MediumGPU: uninitialized resourceNot stated
Patch status by browser (checked 13 November 2026, about 04:10 UTC)
BrowserFixed versionStatus
Chrome (Windows, Mac)157.0.8103.50/.51Released 9 Nov 2026, rolling out
Chrome (Linux)157.0.8103.50Released 9 Nov 2026
Edge for Android157.0.4341.53Released 11 Nov 2026
Edge desktopNot listedMicrosoft working on fix (9 Nov note)

Common mistakes

  • Assuming Chrome is safe because it updates automatically.

    Fix: The update applies only after a relaunch; check About Google Chrome [5].

  • Updating Chrome but forgetting other Chromium browsers.

    Fix: Edge, Opera and other Chromium browsers may also be affected and need their own patched release [4][8].

  • Downloading an 'urgent Chrome update' from a pop-up or email.

    Fix: Only update through the browser's own About Google Chrome page [5].

  • Waiting for exploit details before acting.

    Fix: Google's post says bug details may be restricted until most users are updated [1]; update now.

Frequently asked questions

What is the Chrome zero-day CVE-2026-125350?

A high-severity use-after-free bug in Chrome's XML component that Google says is exploited in the wild [1].

How do I update Chrome right now?

More > Help > About Google Chrome, then click Relaunch [5].

Which versions fix the Chrome zero-day?

157.0.8103.50/.51 for Windows and Mac, 157.0.8103.50 for Linux, or later [1].

Are Edge, Brave and other browsers affected?

Chromium-based browsers may be affected [8]. Edge for Android was fixed on 11 November; desktop Edge had no listed fix on 13 November [4].

Why did CISA add it to the KEV catalog?

Because of evidence of active exploitation; it was added on 10 November 2026 [3].

Is this the first Chrome zero-day of 2026?

No. BleepingComputer reported it as the eighth exploited Chrome zero-day this year [6].

Glossary

Zero-day
A vulnerability exploited by attackers before or as the vendor releases a fix.
Use after free
A memory bug where software keeps using memory it has already released [6].
Chromium
The open-source browser project that Chrome, Microsoft Edge and Opera build on [4][8].
KEV catalog
CISA's list of vulnerabilities with evidence of active exploitation [3].
V8
Chrome's JavaScript engine [1].

Sources

  1. Stable Channel Update for Desktop Google Chrome Releases · 2026-11-09
  2. Google Releases Security Update for Chrome (CC-4887) NHS England Digital · 2026-11-10
  3. CISA Adds Six Known Exploited Vulnerabilities to Catalog CISA · 2026-11-10
  4. Release notes for Microsoft Edge Security Updates Microsoft Learn
  5. Update Google Chrome Google Chrome Help
  6. Google patches eighth Chrome zero-day exploited in attacks this year BleepingComputer · 2026-11-10
  7. CVE-2026-125350 Detail NIST National Vulnerability Database · 2026-11-10
  8. Known Exploited Vulnerabilities Catalog (JSON feed) CISA
Share this guide Telegram WhatsApp X
0 likes

Comments

Top comments

About the Pouyam Team Editorial policy

On Pouyam

Explore Pouyam

Guides are one corner of Pouyam. Here is where to go next.

Quick navigation