Google released a Stable Channel update for Chrome desktop on November 9, 2026, addressing nine security vulnerabilities across browser components, including WebGL, FileSystem, Compositing, GPU, V8, and XML.
The most significant issue is CVE-2026-125350, a high-severity use-after-free vulnerability affecting Chrome's XML component. Google has confirmed that an exploit for this vulnerability exists in the wild, indicating that attackers may already be leveraging the flaw against vulnerable browser installations.
A use-after-free vulnerability occurs when an application continues to access memory after that memory has been released. Depending on the circumstances, this type of memory corruption can cause application crashes or potentially enable arbitrary code execution.
The same update also addresses another XML use-after-free vulnerability, CVE-2026-125346. However, Google specifically identifies CVE-2026-125350 as the vulnerability with an exploit observed in the wild. These are separate vulnerabilities and should not be treated as the same issue.
Google has released the following Stable versions:
Windows: 157.0.8103.50 / 157.0.8103.51
macOS: 157.0.8103.50 / 157.0.8103.51
Linux: 157.0.8103.50
The update is being rolled out over the coming days and weeks. Organizations should not assume that automatic updates have already reached every endpoint. Version verification and browser relaunch are required.
Vulnerability Details
CVE-2026-125350 – Use-After-Free in XML
| Attribute | Details |
|---|---|
| CVE ID | CVE-2026-125350 |
| Product | Google Chrome |
| Component | XML |
| Vulnerability Type | Use-After-Free |
| Severity | High (Google rating) |
| Exploitation Status | Exploit exists in the wild, confirmed by Google |
| Disclosure / Report Date | November 6, 2026 |
| Fixed Version | Chrome 157.0.8103.50/.51 (Windows/macOS), 157.0.8103.50 (Linux) |
The vulnerability is caused by improper memory handling within Chrome's XML component. A use-after-free condition occurs when a program accesses an object or memory region after it has already been released.
Depending on exploitability and memory layout, this class of vulnerability can potentially lead to memory corruption, browser crashes, or execution of attacker-controlled code.
Google has not publicly disclosed detailed technical exploitation steps or the exploit's delivery mechanism in the advisory. It has, however, explicitly confirmed that an exploit exists in the wild.
This confirmation makes CVE-2026-125350 an immediate patching priority for organizations using Chrome.
CVE-2026-125346 – Separate XML Use-After-Free Vulnerability
The same Stable update addresses another high-severity use-after-free vulnerability in the XML component:
| Attribute | Details |
|---|---|
| CVE ID | CVE-2026-125346 |
| Component | XML |
| Vulnerability Type | Use-After-Free |
| Severity | High |
| Researcher | Arni Hardarson, Neonix Security |
| Report Date | October 12, 2026 |
Although both vulnerabilities affect the XML component, Google only explicitly confirmed in-the-wild exploitation for CVE-2026-125350. No equivalent exploitation confirmation was provided for CVE-2026-125346 in this release notice.
Additional Security Fixes
Google's November 9 Stable Channel update includes nine security fixes.
| CVE ID | Component | Vulnerability Type | Severity |
|---|---|---|---|
| CVE-2026-125345 | WebGL | Uninitialized Resource | High |
| CVE-2026-125347 | FileSystem | Incorrect Authorization | High |
| CVE-2026-125343 | Compositing | Buffer Overflow | High |
| CVE-2026-125348 | GPU | Out-of-Bounds Write | High |
| CVE-2026-125344 | V8 | Type Confusion | High |
| CVE-2026-125346 | XML | Use-After-Free | High |
| CVE-2026-125350 | XML | Use-After-Free | High |
| CVE-2026-125349 | GPU | Uninitialized Resource | Medium |
| CVE-2026-125342 | GPU | Uninitialized Resource | Medium |
The update therefore addresses seven High-severity and two Medium-severity vulnerabilities. CVE-2026-125350 is the only vulnerability in this release for which Google explicitly states that an exploit exists in the wild.
Affected Products and Fixed Versions
The following versions are listed in Google's November 9 release information.
| Product / Platform | Fixed Version |
|---|---|
| Google Chrome – Windows | 157.0.8103.50 / 157.0.8103.51 |
| Google Chrome – macOS | 157.0.8103.50 / 157.0.8103.51 |
| Google Chrome – Linux | 157.0.8103.50 |
| Google Chrome – Android | 157.0.8103.50 |
| Google Chrome – Extended Stable (Windows/macOS) | 156.0.8078.96 |
Google's Android release notes state that Android receives the same security fixes as the corresponding desktop release unless otherwise specified.
ChromeOS note: The ChromeOS Stable update published on November 6 does not list CVE-2026-125350. Organizations managing ChromeOS devices should monitor subsequent ChromeOS security advisories rather than assuming the desktop fix applies to their fleet.
Potential Impact
Successful exploitation of a browser use-after-free vulnerability may result in:
Memory Corruption: An attacker may manipulate browser memory through the vulnerable XML processing functionality.
Browser Instability: Exploitation attempts may cause Chrome to crash or behave unexpectedly.
Potential Code Execution: Depending on exploit reliability and additional security protections, memory corruption could potentially be leveraged to execute attacker-controlled code.
Browser Compromise: Successful exploitation could compromise the browser process and potentially support further exploitation attempts.
Enterprise Exposure: Unpatched endpoints may remain vulnerable when employees browse attacker-controlled or compromised web content.
The exact exploitation chain, affected configurations, and post-exploitation capabilities have not been publicly detailed in Google's advisory. These impacts describe potential consequences of the vulnerability class and should not be interpreted as confirmed behavior of the currently observed exploit.
Recommendations
Immediate Actions
Update Google Chrome: Upgrade all desktop installations to the fixed versions: 157.0.8103.50/.51 for Windows and macOS, and 157.0.8103.50 for Linux.
Prioritize Vulnerable Endpoints: Treat Chrome installations exposed to untrusted web content as a priority, particularly systems used for administrative access, finance, and privileged business operations.
Verify Browser Versions: Use enterprise browser management or endpoint inventory tools to identify systems still running vulnerable versions.
Restart Chrome: Ensure users relaunch the browser after the update. A downloaded update may not become active until Chrome is restarted.
Review Browser Activity: Investigate unusual Chrome crashes, unexpected child processes, suspicious browser behavior, and abnormal endpoint activity around the time of suspected exploitation.
Monitor Endpoint Telemetry: Review EDR and SIEM alerts involving Chrome process execution, unexpected script interpreters, unusual process relationships, and suspicious outbound connections.
Track Extended Stable Deployments: Organizations using Extended Stable should verify deployment of version 156.0.8078.96 on Windows and macOS.
Monitor Vendor Advisories: Follow Google's Chrome security updates for additional technical details, exploit information, and subsequent fixes.
Preventive Actions
Enable Automatic Updates: Ensure Chrome automatic updates are enabled and that enterprise update policies do not unnecessarily delay security patches.
Maintain Browser Inventory: Continuously track browser versions across managed Windows, macOS, and Linux endpoints.
Implement Browser Security Policies: Restrict unauthorized browser extensions, enforce safe browsing controls, and apply enterprise browser hardening policies.
Strengthen Endpoint Detection: Maintain EDR visibility into browser process activity and suspicious post-exploitation behavior.
Restrict Administrative Privileges: Avoid running browsers with elevated privileges and apply least-privilege access controls to endpoint users.
Improve Patch Management: Establish emergency patching procedures for vulnerabilities confirmed to be exploited in the wild.
Conduct Continuous Threat Hunting: Search historical endpoint and network telemetry for suspicious Chrome activity and correlate findings with the affected browser versions.
MITRE ATT&CK Mapping
| Tactic | Technique ID | Technique |
|---|---|---|
| Initial Access | T1189 | Drive-by Compromise – potential delivery scenario, not confirmed by Google |
| Execution | T1203 | Exploitation for Client Execution – potential exploitation behavior |
The ATT&CK mapping is indicative only. Google has confirmed an in-the-wild exploit but has not publicly disclosed the delivery method or complete exploitation chain.
Conclusion
Google's November 9, 2026 Chrome Stable update addresses nine security vulnerabilities, including CVE-2026-125350, a High-severity XML use-after-free flaw for which an exploit has been confirmed in the wild.
The exploitation confirmation makes this release particularly important for enterprise security teams. Although Google has not yet published detailed exploit mechanics or indicators of compromise, organizations should not wait for additional technical disclosures before applying the available fixes.
Security teams should prioritize Chrome patch deployment, verify browser versions across managed endpoints, ensure users relaunch updated browsers, and monitor endpoint telemetry for suspicious activity.
