Google — Emergency Update for the Eighth Actively Exploited Zero-Day of 2026 (CVE-2026-125350)
Publication date: November 10, 2026
Category: Vulnerability / Browser Security
Introduction
Google has released an emergency security update to address nine vulnerabilities in the Google Chrome web browser, most notably a critical use-after-free flaw residing within the XML component, tracked as CVE-2026-125350. According to official advisories, this vulnerability is actively exploited in the wild, marking the eighth zero-day patched by Google in real-world attacks since the start of 2026. The flaw was independently discovered and reported by an anonymous security researcher on November 6, 2026. Given the presence of functional exploit vectors in the wild, administrators and end-users are strongly advised to update their browsers immediately.
What is CVE-2026-125350? (General Analysis)
CVE-2026-125350 is a memory corruption vulnerability categorized as a Use-After-Free (UAF) flaw located specifically within Google Chrome’s XML parsing and processing subsystem.
In Chromium-based rendering architectures, the XML component handles the loading, structural parsing, and DOM representation of markup data. When these routines process deeply nested or complex data streams, logic errors in object lifecycle management can cause the application to retain references to memory addresses that have already been freed.
- CWE Classification (Reasoned Estimation): CWE-416 (Use After Free).
- CVSS Score and Vector (Reasoned Estimation): CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H — 8.8 (HIGH). While exploitation requires user interaction (visiting a malicious webpage or processing a crafted XML document), successful execution grants remote attackers code execution capabilities within the security context of the renderer process.
How Does It Work? (Technical Analysis)
The exploitation of browser-based use-after-free vulnerabilities generally follows established methodologies designed to bypass sandbox restrictions:
- Initial Infection Flow / Exploit Entry: The attack vector is triggered when a victim visits a malicious web page engineered with crafted XML or HTML structures designed to manipulate Chrome’s memory heap allocation stack. As Chrome processes the document, attack scripts induce the XML component to free a specific memory object while retaining an active dangling pointer.
- Heap Grooming and Code Execution: Through heap manipulation techniques (such as controlled memory padding via mass creation of TypedArrays or strings), the attacker replaces the freed memory slot with malicious, attacker-controlled data structures. When the engine subsequently attempts to access the original pointer reference, it dereferences manipulated data, leading to memory corruption, control flow hijacking, and arbitrary code execution inside the renderer process space.
- Information Withholding: Reflecting standard vendor disclosure policies, Google has restricted specific bug details and exploit references until a majority of the user base has updated their browsers, mitigating the risk of secondary exploitation chains.
Affected Systems / Environments
This vulnerability impacts all Google Chrome builds preceding the latest patch releases, directly affecting secondary browsers built on the Chromium engine. Furthermore, the recurrence of critical vulnerabilities across components like V8 and Skia highlights ongoing systemic risk profiles.
Summary of Recent 2026 Exploited Vulnerabilities
| CVE | Category (CWE) | Impact | CVSS | Vector (summary) |
|---|---|---|---|---|
| CVE-2026-125350 | CWE-416 (Estimated) | Code Execution / Corruption | 8.8 (Est.) | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CVE-2026-2441 | CWE-416 | Code Execution / CSS UAF | 8.8 | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CVE-2026-3909 | CWE-787 | Out of bounds write (Skia) | 8.8 | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CVE-2026-3910 | CWE-94, CWE-119 | Inappropriate implementation in V8 | 8.8 | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CVE-2026-5281 | CWE-416 | Use-after-free in Dawn | 8.8 | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CVE-2026-11645 | CWE-125, CWE-787 | Out of bounds read/write in V8 | 8.8 | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CVE-2026-85046 | CWE-843 | Type confusion in V8 | 8.8 | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CVE-2026-87491 | CWE-787 | Out of bounds write in V8 | 8.8 | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
- Vulnerable Versions: Google Chrome < 157.0.8103.50/.51 (Windows / macOS) and < 157.0.8103.50 (Linux).
- Impacted Platforms: Desktop operating systems (Windows, Apple macOS, Linux) and downstream Chromium-derived browsers (Microsoft Edge, Brave, Opera, Vivaldi).
Mitigation and Detection
Remediation
System administrators and end users must update their browsers immediately. To ensure updates are applied, navigate to More > Help > About Google Chrome and select Relaunch to finalize installation on the following stable versions:
- Windows and macOS: Versions 157.0.8103.50 or 157.0.8103.51.
- Linux: Version 157.0.8103.50.
Detection
Blue Teams should monitor endpoint telemetry for abnormal browser process behavior, such as unexpected renderer crashes accompanied by core dumps, or unauthorized external network requests triggered immediately following the ingestion of untrusted XML resources.
Tactical Note: The continuous discovery of zero-day exploits targeting peripheral data parsing components highlights the critical need for strict web execution policies and endpoint segmentation across corporate assets.
Wrapping Up
The arrival of the eighth actively exploited zero-day in Google Chrome for 2026 reinforces the persistent threat landscape targeting memory corruption flaws within parser subsystems. While Google’s rapid patch deployment is crucial, enterprise defense ultimately hinges on prompt update adoption across all corporate endpoints.
References
- Lakshmanan, R. (2026). Google Issues Chrome Security Update for Eighth Actively Exploited Zero-Day of 2026. The Hacker News. https://thehackernews.com/2026/11/google-issues-chrome-security-update.html
- Google Chrome Releases. (2026). Stable Channel Update for Desktop. https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html
- National Vulnerability Database. (2026). NVD - CVE-2026-2441. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-2441
- National Vulnerability Database. (2026). NVD - CVE-2026-3909. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-3909
- National Vulnerability Database. (2026). NVD - CVE-2026-3910. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-3910
- National Vulnerability Database. (2026). NVD - CVE-2026-5281. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-5281
- National Vulnerability Database. (2026). NVD - CVE-2026-11645. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-11645
- National Vulnerability Database. (2026). NVD - CVE-2026-85046. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85046
- National Vulnerability Database. (2026). NVD - CVE-2026-87491. https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-87491