Innovation

What Google’s Nov. 9 Chrome Update Fixes: CVE-2026-125350, an Exploited XML Flaw

Google released a Chrome fix on Nov. 9 for CVE-2026-125350, an XML flaw it says is exploited in the wild, its eighth Chrome zero-day this year.

By Theo Laurent · November 12, 2026 · 3 min read
What Google’s Nov. 9 Chrome Update Fixes: CVE-2026-125350, an Exploited XML Flaw

Google released a Chrome security update on Monday, Nov. 9, 2026. The update fixes CVE-2026-125350, a high-severity flaw in Chrome’s XML component that Google says is exploited in the wild. The Hacker News, The Register and BleepingComputer reported the update on Nov. 10 and described it as the eighth actively exploited Chrome zero-day patched this year.

The flaw was reported anonymously to Google on Nov. 6, 2026. Google has not published technical details of the bug, and it is keeping them restricted until most users have installed the fix.

The Use-After-Free Flaw and Its Severity

The flaw is a use-after-free bug, meaning the browser keeps using memory after it has been freed. BleepingComputer says the parser frees an object but leaves a pointer to it, so later use of that memory can allow code execution. The Hacker News reports that the CVE record describes a remote attacker running code inside Chrome’s sandbox through a crafted HTML page.

The Hacker News gives a CVSS score of 8.8. The Register and BleepingComputer report a high severity rating without a numeric score.

The fixed builds are 157.0.8103.50 on Linux and 157.0.8103.50 or .51 on Windows and macOS, according to The Hacker News, The Register and BleepingComputer.

The update fixes nine vulnerabilities in total, according to The Hacker News and Qualys. Besides the zero-day, the release includes high-severity flaws in WebGL, FileSystem, GPU, Compositing and the V8 JavaScript engine, according to The Register. Qualys lists each one by CVE number, including CVE-2026-125345 in WebGL and CVE-2026-125344 in V8.

The same release fixes CVE-2026-125346, a second use-after-free bug in the XML component. The Register reports that Arni Hardarson of Neonix Security reported it in October. Google has not said it is being exploited.

Fixed Build
Chrome builds before 157.0.8103.50 are affected, according to The Hacker News. The fixed builds are 157.0.8103.50 on Linux and 157.0.8103.50 or .51 on Windows and macOS, per The Register and BleepingComputer.

Exploitation and Restricted Bug Details

Google says it is aware that an exploit for the flaw exists in the wild. Google has not said who is behind the attacks, and it is keeping bug details restricted until most users update.

Google has also not said who is being targeted, according to The Register. The Register says the restriction is meant to keep attackers from building a working exploit. BleepingComputer reports that the restrictions would also stay in place if the bug is in a third-party library that other projects depend on and that has not yet been fixed.

The Hacker News and Qualys report that CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog. Federal agencies have a Nov. 24, 2026 deadline to apply the patch, according to The Hacker News.

Eight Exploited Chrome Zero-Days in 2026

The Hacker News lists the seven earlier 2026 flaws as CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046 and CVE-2026-87491. Adding CVE-2026-125350 brings the year’s count to eight.

By component, CVE-2026-2441 sits in CSS font feature values, CVE-2026-3909 in the Skia 2D graphics library, and CVE-2026-5281 in Dawn, the WebGPU implementation, according to BleepingComputer. Four of the seven earlier flaws are in the V8 JavaScript engine: CVE-2026-3910, CVE-2026-11645, CVE-2026-85046 and CVE-2026-87491.

The Register reports that Google had patched five exploited flaws by June, and two more V8 bugs in September. That made seven before CVE-2026-125350, which is in the XML component rather than V8.

The Register also reports that Google patched eight in-the-wild Chrome zero-days in 2025. With about two months left in 2026, this year now matches that total.

Google has not said who is behind the attacks, and it is keeping bug details restricted until most users update.

The Fixed Builds and the Update Path

The Hacker News states that Chrome builds before 157.0.8103.50 are affected, and Qualys gives the same threshold. Once the update reaches a browser, the installed build should be 157.0.8103.50 or later.

According to The Hacker News, Chrome users update through More, then Help, then About Google Chrome, and then Relaunch. The same report says other Chromium-based browsers, including Microsoft Edge, Brave, Opera and Vivaldi, should apply fixes when available.

Google says the rollout may take days or weeks to reach every user. BleepingComputer found the update available immediately when it checked. The fixed builds listed here are for desktop.

Continue reading

More from the Edit