# Chrome patches CVE-2026-125350, its eighth zero-day of 2026

> Google fixes nine flaws in Chrome, including CVE-2026-125350, a use-after-free in XML that has already been exploited. How to check your version today.
> By José Maldonado · Cybersecurity · 2026-11-11

An anonymous researcher reported a bug in Chrome last Friday, November 6, and by Monday morning Google already had the patch and an uncomfortable confirmation: someone was using the flaw before a fix existed. It is called CVE-2026-125350, it lives in the component Chrome uses to read XML and it is a use-after-free, the class of memory error that has been fueling the industry's worst afternoons for a decade. With it, the browser adds its eighth exploited zero-day in 2026, the same figure it racked up during all of 2025 and with almost two months still to go.

The update reached the stable channel on November 9. Chrome is left at 157.0.8103.50 and .51 on Windows and macOS, and at 157.0.8103.50 on Linux. The package brings nine fixes, seven of them high severity, and is being distributed in waves over the coming days or weeks.

The official advisory is almost administratively sober: it confirms that an exploit exists, lists the CVEs and thanks the researchers. It does not say who is attacking, whom they are targeting, how the exploit is delivered or what it achieves on the compromised machine. That restraint is deliberate and follows Google's disclosure policy, which withholds details until most users have updated. The practical problem is that it leaves the user with a decision they cannot fully evaluate, while the Hong Kong CERT classifies the package as extremely high risk due to its remote code execution capability.

## A freed pointer and eight zero-days in a year

The flaw is a use-after-free. The browser allocates a block of memory, frees it when it no longer needs it and, because of a management error, keeps a pointer to that area. If an attacker manages to place their own data in the gap before the program reads the pointer again, the browser will interpret that data as its own. In the best case the tab crashes; in the worst, the attacker gains control of the execution flow inside the browser process.

That the affected component is the XML parser has its irony. XML is not the most common format on the modern web, but Chrome still processes it in documents, fonts, sitemaps and various internal flows that the user never identifies as such. This month's package also touches WebGL, the file system, layer compositing, the GPU and the V8 engine. A memory flaw in XML is hard to reach by hand, and that is why the advisory does not explain the vector: publishing the detail would amount to handing the exploit to those who have not yet updated.

A secondary detail that does appear in the fine print: the list of credited researchers includes one anonymous and two external teams, and leaves seven entries signed by Google itself.

The [Chrome stable channel advisory](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html) does list the nine references, and there the second interesting piece appears: CVE-2026-125346, another use-after-free in the same XML component, reported in October by Arni Hardarson, of Neonix Security. Google has not said this second one is being exploited. Two flaws of the same type in the same piece of the browser, in less than a month, is the kind of coincidence that security teams read as technical debt rather than bad luck.

### A frightening figure

The figure of eight deserves context. An exploited zero-day means someone found the vulnerability and used it before a patch existed, or at least before the vendor knew about it. That a browser accumulates eight in a year does not indicate it is less secure than its rivals, but that it is the most profitable target in the ecosystem: it has more users than any operating system and runs on top of all of them. Attackers do not choose the weakest target, they choose the one that gives access to the most people.

The comparison with 2025 is not reassuring either. Google closed last year with eight exploited zero-days in Chrome and has now matched the count in November, with the high season of shopping and gifts still to come. The pattern of recent months suggests that exploitation has been industrialized: flaws are detected earlier, weaponized faster and used in short, surgical campaigns before the patch closes the window.

Eight in a year is not a statistical anomaly, it is a toll the ecosystem pays for sharing a single engine. The browser everyone uses is also the one everyone tries to break.

For the user, the practical consequence is that updating the browser has stopped being a maintenance task and become a security routine with a date. Chrome does not update itself if the machine is never shut down or if an extension blocks the process, something more common than it seems in corporate fleets. On Linux, moreover, the package may arrive packaged by the distribution weeks after the advisory if the user depends on the system repository instead of Google's binary.

## Which version do you need to have and how do you check it?

Platform

Version with the fix

Status

Chrome on Windows and macOS

157.0.8103.50 / .51

Rolling out

Chrome on Linux

157.0.8103.50

Rolling out

Extended Stable channel

156.0.8078.96

Rolling out

Chrome for Android

157.0.8103.50

Rolling out

ChromeOS stable

No advisory listing the CVE

Pending

The procedure has not changed: three-dot menu, Help, About Google Chrome. The browser downloads the update and offers to restart; tabs are restored afterwards. Distribution goes in waves, so the version number may take time to appear even if Google has already published the fix. The table matters because the Android update keeps the same fixes as the desktop and because Extended Stable channel users see a different version number, a common source of confusion when someone compares against a screenshot.

ChromeOS is the obvious gap. The system's latest stable update, M-156 on November 6, does not mention CVE-2026-125350, and Monday's beta note carried no security details either. Anyone working on a Chromebook depends on Google publishing that version, and in the meantime it is best to assume that the engine opening tabs on the device is still vulnerable.

## What the update drags along and does not appear in the advisory

Chrome does not live alone. Edge, Brave, Opera, Vivaldi and a long list of smaller browsers are built on the same code, and all of them need their own update to receive the fix. The same logic applies to desktop applications built with Electron (chat clients, editors, development tools) that embed Chromium and inherit its flaws without the user thinking of them when reading that bit about updating Chrome. A patch applied in the browser leaves much of the real attack surface of a modern desktop uncovered.

Electron, on the other hand, is the least discussed door and the hardest to close. The user does not control when the developer of their favorite application recompiles with the new Chromium, and an abandoned client can spend months on the old engine without anyone noticing until someone exploits it.

For the corporate environment there are two questions that deserve an answer this week. The first is whether Chrome deployment is managed and with what delay the stable channel reaches the machines. The second is whether anyone has inventoried the Electron applications running on workstations, because those do not appear in the operating system's update panel or in the usual compliance reports. Neither of the two is resolved by reading Google's advisory.

## The window Google cannot close

The policy of withholding details until most people have updated protects many and leaves just as many in the dark. An administrator who needs to justify an urgent maintenance window has no argument beyond the CVE number and the word exploited. An analyst who wants to know whether their organization was exposed will not find the vector in the advisory either, because publishing it would turn the patch into a manual for the next attacker.

That balance is reasonable and at the same time insufficient, and it is worth saying so plainly. The only measure that truly reduces exposure is the one that has been repeated for years and is still not carried out with discipline: an updated browser, without delay, and an honest list of every application that has a browser engine inside it. The rest is risk management, that is, knowingly choosing what to leave open.

This month's calendar makes it clear. The [CVE-2026-98432 in the Linux kernel](https://observatorioblockchain.com/en/cybersecurity/cve-2026-98432-kernel-tcp-ubuntu-rhel-sin-parche/) is still awaiting a patch in Debian and RHEL a week after its advisory, and the [fake APT package that gave root](https://observatorioblockchain.com/en/cybersecurity/apt-cve-2026-109518-debian-ubuntu-root/) showed that even the updater can be the vector.
