Google has rushed out an emergency fix for Google Chrome after confirming that attackers are already exploiting a serious flaw in the browser. The vulnerability, tracked as CVE-2026-125350, is a use-after-free bug in Chrome's XML handling — the kind of memory-safety flaw that can let a malicious web page corrupt the browser's memory and run code on a victim's machine.
Google disclosed the flaw in its November 9 Stable Channel update for desktop Chrome, with a single line that security teams never want to read: the company is aware that an exploit for CVE-2026-125350 exists in the wild. The bug was reported anonymously on November 6, and Google shipped the fix just three days later — a fast turnaround for an actively exploited flaw.
The fix is included in Chrome 157.0.8103.50 and 157.0.8103.51 for Windows and macOS, and 157.0.8103.50 for Linux. Organisations on the Extended Stable channel get the patch in version 156.0.8078.96. Chrome downloads updates in the background, but the fix only takes effect once the browser is relaunched — so the update is not truly installed until users restart Chrome.
The eighth Chrome zero-day of 2026
CVE-2026-125350 is the eighth actively exploited Chrome zero-day patched in 2026, tying the total Google fixed across all of 2025 — with nearly two months of the year still to go. The flaw sits in libxslt, the XML library Chrome bundles for XSLT processing, specifically in its direct pattern-matching cache. A crafted page can trigger the memory error, though Google has not said whether the exploit escapes Chrome's sandbox or what kind of sites are serving it.
The same release fixes eight other security issues, including a second XML use-after-free flaw, CVE-2026-125346, reported on October 12 by Arni Hardarson of Neonix Security. That second bug is not known to be exploited. Google is restricting access to the underlying Chromium bug report and withholding technical details until most users have updated — standard practice to avoid handing attackers a recipe.
CISA adds the flaw to its must-fix list
The US Cybersecurity and Infrastructure Security Agency added CVE-2026-125350 to its Known Exploited Vulnerabilities catalogue on November 10, giving federal agencies until November 24 to patch. CISA's listing is a strong signal for everyone else too: when a flaw is confirmed exploited and added to the catalogue, it is no longer a theoretical risk.
Chromium-based browsers share Chrome's engine, but each vendor ships its own fix on its own schedule. Microsoft said on November 9 that it is aware of the exploits and is working on a security fix for Edge, so Edge users should watch for an update in the coming days. With Chrome holding roughly 67 percent of the desktop browser market, according to Statcounter's October figures, the vulnerable population is enormous — and the window between disclosure and patching is exactly when attacks tend to spike.
What to do now
The advice is simple and urgent: update Chrome to version 157.0.8103.50 or later, then restart the browser. On desktop, that means opening the menu, going to Help and then About Google Chrome, and relaunching when prompted. IT teams managing fleets should push the update and, where possible, enforce a relaunch — an update downloaded but not applied leaves the flaw wide open.
Google has published no indicators of compromise and no information about who is behind the attacks or who is being targeted. That silence is normal after an emergency patch, but it also means users cannot check whether they have already been hit. For now, the only reliable defence is the patch itself — and the restart that activates it.



