Google Patches Its Eighth Actively Exploited Chrome Zero-Day of 2026
Google fixed CVE-2026-125350, a use-after-free in Chrome's XML component that attackers are already exploiting, in version 157.0.8103.50 on 9 November.

On this page
Key takeaways
- Google released Chrome 157.0.8103.50 on 9 November 2026 to fix CVE-2026-125350, a high-severity use-after-free in the browser's XML component.
- Google says an exploit for the flaw exists in the wild, making it the eighth actively exploited Chrome zero-day of 2026.
- The flaw allows a remote attacker to execute arbitrary code inside Chrome's sandbox through a crafted HTML page.
- CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on 10 November and set a 24 November deadline for federal civilian agencies.
- Users should update to 157.0.8103.50 or later and relaunch the browser; other Chromium-based browsers need their own fixes.
Google released an emergency Chrome update on Monday 9 November 2026 to fix nine security flaws, including one that attackers are already using. The actively exploited bug, tracked as CVE-2026-125350, is a high-severity use-after-free vulnerability in Chrome's XML component. Google rates it 8.8 on the CVSS scale.
Related reading: AI Agents Found a Zero-Day in MONAI Label and Rooted a University Server · China-Linked Hackers Exploited a vCenter Zero-Day Weeks Before the Patch.
The flaw affects Chrome before version 157.0.8103.50. Google shipped 157.0.8103.50 and 157.0.8103.51 for Windows and macOS, and 157.0.8103.50 for Linux. The company says it is aware that an exploit exists in the wild, but it has not published details about how the flaw is being abused or who is behind the attacks.
The update is the eighth actively exploited Chrome zero-day Google has patched in 2026. That pace makes browser patching one of the few security chores where a delay of days, rather than months, can matter.
What the flaw does
CVE-2026-125350 is a use-after-free bug. That class of flaw happens when a program frees a chunk of memory and then keeps using a pointer to it. An attacker who can control what gets written into the freed memory can sometimes redirect execution or corrupt data.
In Chrome's case, the vulnerable code sits in the XML component. Google's advisory says a remote attacker can execute arbitrary code inside the sandbox by convincing a user to open a crafted HTML page. The "inside the sandbox" wording matters: the attacker gets code execution in the renderer process, not automatic control of the whole machine. A full compromise would still need a sandbox escape, which is a separate and harder step.
The bug was reported anonymously on 6 November 2026, three days before the fix shipped. Google has not named the researcher. It also has not said whether the exploit was used in targeted attacks against a specific industry, or whether it was found in a broader campaign.
The eighth Chrome zero-day of the year
Google has now fixed eight Chrome zero-days that were exploited in the wild in 2026. The earlier list includes CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046 and CVE-2026-87491.
That count is unusual but not unprecedented. Chrome's market share makes it a constant target, and the browser's large attack surface, which includes XML parsing, graphics, JavaScript and PDF rendering, gives researchers and attackers many places to look. Google pays for vulnerability reports through its bug bounty programme, but a single anonymous report three days before a patch suggests the company was reacting to an active campaign rather than a routine disclosure.
The other eight flaws in the 9 November update were not described as exploited. Google typically withholds technical details until most users have updated, to slow down the development of working exploits. That practice helps defenders, but it also means administrators have little information beyond the severity rating when they decide how quickly to patch.
The 9 November update fixed nine vulnerabilities in total. Only CVE-2026-125350 was described as actively exploited. Google has not published the technical details of the other eight.
Why browser zero-days are different
A browser zero-day is valuable because the browser is where most people do their work, banking, shopping and reading. An attacker who can run code in a renderer can steal session cookies, read page content, capture keystrokes and reach internal web applications that are only accessible from the victim's machine.
The sandbox limits the damage, but it does not eliminate it. Many real-world attacks chain a renderer bug with a separate sandbox escape and a privilege escalation. Even without the full chain, a renderer compromise can be enough to steal credentials or pivot through a corporate web app.
Chrome's update cadence has also changed how these bugs are exploited. Google now ships security fixes more frequently, which shortens the window between disclosure and patching. Attackers have responded by moving faster: the 6 November report and the 9 November fix left a three-day gap, and CISA added the flaw to its catalogue the next day.
Enterprises are the weak point in that race. Managed browsers often run behind the stable channel, and a fleet that updates on a monthly cycle can stay exposed for weeks. Organisations that allow browser extensions add another layer of risk, because an extension with broad permissions can read page content even when the browser itself is patched.
CISA sets a 24 November deadline
The U.S. Cybersecurity and Infrastructure Security Agency added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on 10 November 2026. The catalog entry requires federal civilian agencies to apply the patch by 24 November.
The KEV deadline is a useful signal for everyone else. It means CISA has evidence of exploitation, not merely a theoretical risk, and it sets a minimum bar for patching. Private organisations are not bound by the deadline, but a two-week window is a reasonable target for a browser flaw that is already being used.
CISA added the Chrome bug in a batch of six known exploited vulnerabilities on 10 November. The others included flaws in Barracuda Email Security Gateway, Microsoft Outlook, Cisco BroadWorks and Openwave Webtop. The clustering is a reminder that attackers rarely rely on a single bug; they mix browser, email and edge-device exploits in the same campaign. The Check Point Gaia flaw that CISA flagged three days later is another example of a vulnerability moving from disclosure to federal deadline in under a week.
How to check and update
On Windows, macOS and Linux, open Chrome and go to More > Help > About Google Chrome. The browser will check for updates and show the installed version. If an update is available, click Relaunch. The fixed versions are 157.0.8103.50 or later on Windows and macOS, and 157.0.8103.50 on Linux.
Chrome usually updates itself in the background, but the relaunch step is what actually applies the new version. A browser that has been open for weeks may be running an old build even if the update has already downloaded. Closing all Chrome windows and reopening the browser is the simplest way to be sure.
Other Chromium-based browsers, including Microsoft Edge, Brave, Opera and Vivaldi, share the underlying engine but ship fixes on their own schedules. Check each browser's update menu and install the latest version. On managed devices, the organisation's patch tooling may handle the update, but it is worth confirming that the browser has actually restarted.
Android and iOS Chrome have separate release trains. Google's 9 November advisory covers desktop Chrome. Mobile users should check their app store for the latest Chrome release, though the desktop flaw's exploitation pattern, a crafted HTML page, is not platform-specific.
What we still do not know
Google has not said who is exploiting the flaw, what the campaign targets, or whether the exploit has been used in espionage or financially motivated attacks. The company has also not published indicators of compromise, which makes it hard for defenders to hunt for past exploitation.
The lack of detail is normal for an actively exploited zero-day, but it leaves several questions open. Was the exploit used against a narrow set of targets, or is it circulating more widely? Did the attacker chain it with a sandbox escape? Was the anonymous report from a victim, a researcher or a broker?
Those answers may come later, once Google lifts its restrictions on the bug details. By then, most users should have updated, which is the point of the delay.
What to watch
The first thing to watch is patch adoption. Chrome's automatic updater helps, but a large share of users keep browsers open for days or weeks without relaunching. Enterprise patch dashboards should show the fixed version rolling out over the next two weeks.
The second is whether other vendors disclose related flaws. Chromium-based browsers often patch the same underlying bug shortly after Google, and a delay creates a window for attackers who know the flaw exists but not which browsers are still vulnerable.
The third is the exploit's afterlife. Once Google publishes technical details, security researchers will build proofs of concept and attackers will fold them into exploit kits. A browser flaw that is actively exploited before patch details are public tends to remain useful for months.
For most people, the practical response is simple: update Chrome, relaunch it, and check that the version number has changed. The rest is context.
Updating Chrome does not remove a sandbox escape or a separate privilege-escalation flaw. If you suspect a machine was targeted, look for unusual browser extensions, new admin accounts and outbound connections, not just the Chrome version.
Tags
Frequently asked questions
- What is CVE-2026-125350?
- It is a high-severity use-after-free vulnerability in Google Chrome's XML component. A remote attacker can execute arbitrary code inside the browser sandbox by convincing a user to open a crafted HTML page.
- Which Chrome versions are affected?
- Chrome versions before 157.0.8103.50 are affected. Google released 157.0.8103.50 and 157.0.8103.51 for Windows and macOS, and 157.0.8103.50 for Linux.
- Is CVE-2026-125350 being exploited?
- Yes. Google says it is aware that an exploit exists in the wild. It has not published details about the attacks, the victims or who is behind them.
- Do I need to update Edge, Brave or Opera too?
- Yes, eventually. Those browsers use Chromium, but their vendors ship fixes on their own schedules. Check each browser's update mechanism and install the latest version.








