Skip to main content

Morning Overview

Google fixes Chrome’s eighth zero-day of 2026 and CISA tells federal agencies to update

For anyone who opened Chrome on a laptop at work in the second week of November, the browser’s update prompt carried more weight than usual. A flaw in the way Chrome handles XML data was already being used in attacks before Google had a fix ready, and the federal government has since told its own agencies to install the patch.

Google released Chrome 157.0.8103.50 on Nov. 9, 2026, to close that hole, tracked as CVE-2026-125350. It is the eighth Chrome vulnerability this year that Google has said was exploited in the wild before a patch shipped, and the Cybersecurity and Infrastructure Security Agency added it to its Known Exploited Vulnerabilities catalog the next day.

What Google’s release notes say about CVE-2026-125350

The entry sits in the Chrome Releases post dated Nov. 9, signed by Srinivas Sista of Google Chrome. It lists the bug as “High CVE-2026-125350: Use after free in XML” and carries a line Google reserves for the worst cases: “Google is aware that an exploit for CVE-2026-125350 exists in the wild.”

A use-after-free flaw occurs when software keeps using a piece of memory after releasing it, which can let an attacker run code of their choosing. According to The Hacker News, the bug scores 8.8 on the CVSS severity scale, and the Nov. 9 update patches nine vulnerabilities in total.

The release notes credit two reports. Arni Hardarson of Neonix Security reported the bug on Oct. 12, and an anonymous researcher reported it on Nov. 6, three days before the fix shipped. Google has not published who is exploiting the flaw or against whom, and the release notes give no technical description beyond the component name and the bug class.

Fixed builds for Windows, Mac and Linux

The patched versions are 157.0.8103.50 and 157.0.8103.51 for Windows and Mac, and 157.0.8103.50 for Linux. Canada’s Cyber Centre advisory describes the exposure from the other side: as of Nov. 9, Chrome stable on Windows and Mac before 157.0.8103.50/.51, and on Linux before 157.0.8103.50, is affected.

Chrome normally updates itself, but the fix takes hold only after a restart. The Hacker News gave the manual route: open the menu, choose Help, then About Google Chrome, and select Relaunch once the download finishes.

Google followed with another stable release two days later, and anyone checking a fleet should read build numbers rather than assume. The Nov. 11 post lists version 157.0.8103.78/.79 for Windows and Mac and 157.0.8103.78 for Linux, with its own set of security fixes. The post does not mention CVE-2026-125350 or in-the-wild exploitation, so the Nov. 9 build is the one that carries the zero-day fix, and anyone on the newer build is past it.

CISA’s catalog listing and the federal deadline

Canadian officials recorded the U.S. step. In its advisory AV26-1140, the Canadian Centre for Cyber Security said Google indicated the flaw is exploited in the wild and that CISA added it to the Known Exploited Vulnerabilities catalog on Nov. 10, 2026.

Listing in that catalog is what turns a vendor patch into an agency obligation. Under CISA’s binding operational directive for the catalog, civilian federal agencies must remediate listed flaws by a set date. The Hacker News reported that federal agencies must apply the patch by Nov. 24, 2026. CISA’s own catalog page could not be loaded for this report, so that date rests on The Hacker News and should be checked against the catalog entry.

The two-week window is typical for a Chrome entry. When CISA added two earlier Chrome flaws, CVE-2026-3909 and CVE-2026-3910, Security Affairs reported on Mar. 13 that agencies were ordered to fix them by Mar. 27, also fourteen days out. The catalog entry binds federal civilian agencies, not private companies, so for an organization managing hundreds of Chrome installs the practical question is whether the Nov. 9 build or the later Nov. 11 build has reached every machine, including laptops that stay asleep or offline for days.

A long run of Chrome zero-days in 2026

The count of eight is Google’s pace for the year, as tallied by BleepingComputer in its headline, “Google patches eighth Chrome zero-day exploited in attacks this year.” Eight in under eleven months averages one roughly every five to six weeks.

The context for this patch is a heavy release cycle. The Nov. 3 release that promoted Chrome 157 to the stable channel included 212 security fixes, per the Chrome Releases post of that date, with credits spanning outside researchers and Google staff. CVE-2026-125350 does not appear in that list; it arrived six days later as an out-of-band fix.

What remains unanswered is the part only the attackers and the reporters know: how the XML flaw was reached from a web page, who was targeted, and whether the exploit has spread beyond its first operators. Google’s notes say only that it exists, and the Nov. 24 federal deadline falls three days after publication of this article.

This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.


More from Morning Overview


Morning Overview is reader-supported. Some links in our articles are affiliate links, and we may earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Full disclosure.