Tuesday, November 17, 2026
AI desk
/
/
Update Chrome Now: Google Patches an Actively Exploited XML Zero-Day

Update Chrome Now: Google Patches an Actively Exploited XML Zero-Day

Google patched an actively exploited Chrome XML zero-day. Update to Chrome 157.0.8103.50 or later on Windows, Mac, Linux, and Android.
Last updated
November 17, 2026
7 min read
Fact-checked

Photo: TechJournal

Share

Quick Answer

Google has patched CVE-2026-125350, an actively exploited high-severity Chrome flaw that can execute code inside the browser sandbox through a crafted HTML page. Update Chrome to version 157.0.8103.50 or later immediately, then restart the browser to apply the fix. Windows and macOS users receive .50 or .51 builds, while Linux and Android receive .50 builds.

Key Takeaways

  • Google released the emergency Chrome security update on November 9, 2026.
  • CVE-2026-125350 is a high-severity use-after-free flaw in Chrome’s XML component.
  • Google confirmed that an exploit for the vulnerability exists in the wild.
  • Chrome 157.0.8103.50 or later contains the fix for affected desktop and Android users.
  • CISA added the flaw to its Known Exploited Vulnerabilities catalog with a November 24 federal remediation deadline.

What is the Chrome zero-day update for CVE-2026-125350?

Google’s Chrome zero-day update fixes CVE-2026-125350, a high-severity use-after-free vulnerability in Chrome’s XML component. Google released the emergency patch on November 9, 2026, and said it was aware that an exploit for the flaw exists in the wild. Google’s Chrome release notes confirm that the desktop update includes fixes for nine security vulnerabilities.

CVE-2026-125350 matters because an attacker can use a crafted HTML page to execute arbitrary code inside Chrome’s sandbox. The browser sandbox is a security boundary intended to restrict what a compromised browser process can access. Sandbox execution does not automatically mean that an attacker controls the entire computer, but it can provide a foothold that attackers may attempt to combine with other flaws.

Chrome users should treat active exploitation as the deciding factor. A vulnerability does not need to affect every user before it becomes urgent, because a malicious page can reach users through links, compromised sites, ads, messages, or other web content. The practical response is to install the current Chrome version, restart the browser, and avoid delaying the update until the next routine patch cycle.

Which Chrome versions contain the security fix?

Chrome 157.0.8103.50 or later contains the fix for CVE-2026-125350. Google shipped Chrome 157.0.8103.50/.51 for Windows and macOS, Chrome 157.0.8103.50 for Linux, and Chrome 157.0.8103.50 for Android. The different Windows and macOS build suffixes are normal release packaging details, not different vulnerability verdicts.

PlatformPatched Chrome versionWhat users should do
Windows157.0.8103.50 or 157.0.8103.51Update Chrome and relaunch the browser.
macOS157.0.8103.50 or 157.0.8103.51Update Chrome and relaunch the browser.
Linux157.0.8103.50Install the available Chrome package update and restart Chrome.
Android157.0.8103.50Update Chrome through Google Play, then reopen the app.

Google said Android receives the corresponding desktop security fixes unless otherwise noted. Chrome users should still confirm the installed version rather than assuming automatic updates have completed, especially on devices that have been offline, managed by an employer, or set to restrict background app updates.

Why is CVE-2026-125350 considered high risk?

CVE-2026-125350 is high risk because the vulnerability has evidence of active exploitation and can allow arbitrary code execution inside Chrome’s sandbox through crafted HTML content. The official CVE record identifies the issue as a use-after-free flaw in Chrome’s XML component that affects versions before 157.0.8103.50.

A use-after-free vulnerability occurs when software continues to access memory after that memory has been released or reassigned. That unsafe memory access can produce unexpected program behavior. In this case, the affected code is part of Chrome’s XML handling, which matters because browsers process web content continuously while users browse ordinary pages.

Chrome’s sandbox reduces the impact of many browser attacks, but the sandbox is not a reason to postpone the patch. Attackers commonly pursue browser flaws because a successful initial compromise can be valuable on its own, and additional vulnerabilities can sometimes increase the final impact. Users who want a broader explanation of how layered defenses work can review core cybersecurity protections alongside the update guidance.

How do you update Chrome safely now?

Chrome users can update Chrome by opening the browser menu, selecting Help, choosing About Google Chrome, and allowing the browser to check for and install the available update. Restart Chrome after the download completes, because an installed security update does not protect the active browser session until Chrome relaunches.

  1. Open Google Chrome on the device you use for browsing.
  2. Select the three-dot menu in the upper-right corner.
  3. Choose Help, then select About Google Chrome.
  4. Allow Chrome to download the available version 157.0.8103.50 update or a later version.
  5. Restart Chrome when the browser offers the Relaunch option.
  6. Check the displayed version after Chrome reopens.

Android users should update Chrome through the Google Play Store and reopen the app after installation. Do not download Chrome installers, APK files, or supposed emergency patches from pop-up ads, unsolicited messages, or file-sharing sites. The safe source is the browser’s built-in updater, the official app store, or an organization’s approved software-management tool.

Chrome users should stop and contact their workplace IT administrator if a managed work device does not offer the update, blocks the update, or displays a policy message. Employees should not bypass company controls by installing an unofficial browser copy, because that can create a separate security and data-management problem.

Who needs to install the Chrome patch first?

Chrome users who browse the web on Windows, macOS, Linux, or Android should install the patch as soon as it becomes available. Active exploitation means attackers have already used or developed an exploit for the vulnerability, so waiting for a monthly maintenance window creates unnecessary exposure for devices that use Chrome regularly.

Organizations should prioritize devices used for work email, financial services, administration portals, software development, and access to sensitive customer or employee data. Those systems can expose more valuable accounts or files if an attacker gains browser-level access. The update is also important for users who rely on Chrome profiles that sync passwords, payment methods, extensions, bookmarks, and browsing data across devices.

Users with browser extensions should update Chrome first and then review unfamiliar extension activity separately. A browser update fixes the reported XML flaw, but it does not remove a malicious extension or reverse a prior account compromise. Recent incidents involving compromised developer tools, including a trojanized coding extension, show why software updates and extension hygiene are separate security tasks.

What does CISA’s exploited-vulnerabilities listing mean?

CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on November 10, 2026, with a federal civilian executive branch remediation deadline of November 24, 2026. The CISA catalog entry is significant because the agency uses the list for vulnerabilities with evidence of exploitation that warrant prioritized remediation.

The November 24 deadline applies to the federal agencies covered by CISA’s binding operational directive, not automatically to every consumer or private company. Even so, the listing gives consumers and private-sector administrators a clear signal that the flaw is not merely theoretical. Chrome users do not need to wait until that date, because the patched browser version is already available.

CISA’s listing does not establish that every Chrome user has been targeted or compromised. The catalog identifies known exploited vulnerabilities, while the risk to a specific person depends on browser version, exposure to malicious content, and other security controls. The most sensible approach is to update promptly, keep the operating system current, and review important accounts if suspicious browser activity appears after visiting an untrusted site.

How is this patch different from Chrome’s earlier November update?

Chrome’s November 9 emergency patch is a separate event from the site’s earlier coverage of Chrome 157 security fixes. The new release specifically addresses CVE-2026-125350 after Google confirmed active exploitation, while the earlier Chrome 157 security update covered 213 reported security bugs.

The distinction matters because version numbers alone can be misleading when browser vendors issue multiple releases close together. Chrome 157.0.8103.50 and .51 are the versions tied to the actively exploited XML flaw, so users should verify the full version number rather than relying only on the major version label, Chrome 157.

Independent reporting described CVE-2026-125350 as Google’s eighth Chrome zero-day patched after evidence of active exploitation in 2026. BleepingComputer’s reporting provides that broader count. The practical lesson is not that users need to track every zero-day, but that browser update prompts deserve prompt attention when active exploitation is confirmed.

What should you do after Chrome finishes updating?

Chrome users should restart the browser, confirm that the installed version is 157.0.8103.50 or later, and close any older Chrome windows that remain open. A relaunch matters because browser processes can continue running in the background until every window is closed, particularly when Chrome is configured to keep background apps active.

Chrome users should also review recent downloads, unfamiliar extensions, and unexpected sign-in alerts if they clicked a suspicious link or visited an untrusted page before updating. Those checks are precautionary, not proof that the XML vulnerability affected the device. A browser patch blocks the known flaw in the updated version, but it cannot undo actions that occurred before the update was installed.

Users who suspect account theft should change passwords from a known-safe device, enable multi-factor authentication where available, and review active sessions in the affected accounts. Users who see repeated crashes, unrecognized browser extensions, or signs of malware after updating should run their security software and contact a qualified support provider if the problem continues. Do not attempt to diagnose a potentially compromised work device by installing unapproved cleanup tools.

FAQ

Do I need to update Chrome if it updates automatically?

Chrome users should still check for the update manually because automatic updates can wait until the browser restarts. Confirm that Chrome shows version 157.0.8103.50 or later after reopening the browser.

Is CVE-2026-125350 actively exploited?

Google confirmed that an exploit for CVE-2026-125350 exists in the wild. CISA also added the Chrome flaw to its Known Exploited Vulnerabilities catalog, which indicates evidence of exploitation.

Does the Chrome zero-day affect Android phones?

Chrome for Android receives the corresponding desktop security fixes unless Google notes an exception. Android users should install Chrome 157.0.8103.50 or later through the Google Play Store.

Can a malicious website exploit the Chrome XML flaw?

CVE-2026-125350 can allow a remote attacker to execute arbitrary code inside Chrome’s sandbox through a crafted HTML page. Chrome users should update promptly and avoid downloading files or browser updates from untrusted pages.

Does restarting Chrome matter after the update downloads?

Chrome must restart to load the patched browser version into active use. Chrome users should select Relaunch when the update finishes and then confirm the installed version.

Share this guide
Facebook
X
LinkedIn
Written by
Priya Sharma is a cybersecurity analyst and tech writer who covers digital privacy, online safety, and creative technology tools. She holds a CompTIA Security+ certification and writes about making security accessible for non-technical audiences. She’s passionate about the intersection of AI and creative work.

In this article

The AI Brief

Guides like this, every Friday.

One email. No hype cycle.

Essential guides