For the eighth time this year, Google has had to rush out a Chrome fix for a flaw that attackers were already using. The company says an exploit for the newest bug exists in the wild, and it has kept the technical details under wraps while the world’s most popular browser updates itself.
Read next on Morning Overview: The FAA wants $2.39 million from a flight school it says flew a Cessna about 280 times with an unapproved part
The flaw, tracked as CVE-2026-125350, is fixed in Chrome 157.0.8103.50 and later. It is the eighth actively exploited Chrome zero-day patched since January, and federal agencies have been ordered to install the fix by November 24.
CVE-2026-125350, a use-after-free bug in Chrome’s XML code
Google released the update on Monday, November 9, patching nine security vulnerabilities, according to The Hacker News. The exploited flaw is rated high severity, with a CVSS score of 8.8, and is described as a use-after-free bug in Chrome’s XML component. The public description in the CVE record says it “allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page” in versions before 157.0.8103.50.
A use-after-free bug happens when a program keeps using a piece of memory after it has been released. An attacker who can control what fills that memory can sometimes steer the program into running code of the attacker’s choosing. In Chrome’s case, the “crafted HTML page” in the description means a malicious website is enough to trigger the flaw. Code running “inside the sandbox” is still walled off from much of the computer, but attackers often chain a bug like this with a second flaw to break out.
An anonymous security researcher reported the bug to Google on November 6, 2026, only days before the fix shipped. Google said it is “aware that an exploit for CVE-2026-125350 exists in the wild” but has not said who is using it or against whom. “Access to bug details and links may be kept restricted until a majority of users are updated with a fix,” the company said in its release notes, a standard practice that gives users time to update before other attackers can copy the technique.
Google added that it would keep those restrictions in place if the bug turned out to live in a third-party library that other software projects also depend on but have not yet fixed. That caveat matters for XML parsing, which is handled by code shared well beyond Chrome. The other eight vulnerabilities fixed in the same release were not reported as exploited, but the update delivers all nine fixes at once, so installing it closes the exploited flaw and the rest together. Google has not said whether the attacks were broad or aimed at a small number of chosen targets, a pattern common to commercial spyware campaigns.
Eight exploited Chrome zero-days in 2026
The Hacker News counts eight actively exploited Chrome zero-days fixed since the start of the year: CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046, CVE-2026-87491 and now CVE-2026-125350. Each was a flaw that attackers found and used before Google could ship a patch.
The federal government is treating the newest one as urgent. The Cybersecurity and Infrastructure Security Agency added the Chrome flaw to its Known Exploited Vulnerabilities catalog, which requires federal civilian agencies to apply the patch by November 24, 2026. CISA adds a bug to that list only when it has evidence of active exploitation, and private companies often use it as a priority list for their own patching.
The fixed versions are 157.0.8103.50 and 157.0.8103.51 for Windows and macOS and 157.0.8103.50 for Linux, according to a summary of the release by Deskmodder. The same underlying code is shared by other Chromium-based browsers, including Microsoft Edge, Brave, Opera and Vivaldi, which ship their own updates on their own schedules.
How to make sure the patch is installed
Chrome downloads updates automatically in the background, but it cannot finish installing them until the browser is closed and reopened. People who rarely restart Chrome, or who leave dozens of tabs open for weeks, can end up running an older, vulnerable version long after a fix is available.
Google’s Chrome help page on updates explains the check: open the three-dot menu, choose Help, then About Google Chrome. The page shows the installed version and starts any pending update; a Relaunch button finishes the job. A version number of 157.0.8103.50 or higher means the fix is in place. On Android and iPhone, Chrome updates come through the Google Play Store and Apple’s App Store.
Users of Edge, Brave, Opera and Vivaldi should check those browsers’ own About pages, since each vendor must pull in Google’s fix and release it separately. Until they do, the same malicious page that targets Chrome could target them as well. With seven weeks left in 2026, Google’s count of exploited Chrome zero-days for the year is already at eight, and it may not be finished.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
More from Morning Overview
- Winter weather advisories cover I-80, I-70 and the Bighorns with up to 15 inches of snow
- Arizona’s governor declared a statewide emergency after Flagstaff logged its wettest Nov. 1 on record
- Zero Motorcycles unveiled an electric motorcycle targeted at under $8K and a street-legal dirt bike at EICMA
- New FCC rules on how people can stop robocalls and texts take effect Nov. 25