
Chrome Zero-Day CVE-2026-125350: Patch to 157.0.8103.50 - shattered.io
Google has confirmed that attackers are exploiting CVE-2026-125350, a High-severity use-after-free bug in Chrome's XML handling, with the fix rolling out in Chrome 157.0.8103.50 on November 9, 2026.
The vulnerability affects all Chrome builds older than 157.0.8103.50 on both desktop and Android platforms. A remote attacker can exploit this flaw by using a specially crafted webpage to run arbitrary code inside Chrome's sandbox environment. While Google has acknowledged active exploitation in the wild, they have not labeled it as a zero-day in their official release notes.
This incident follows a pattern seen in September when Google patched CVE-2026-85046 in the V8 engine after exploitation was discovered. The current XML bug was reported twice—first by Arni Hardarson of Neonix Security on October 12, and then by an anonymous researcher on November 6—suggesting multiple parties may have discovered the vulnerability independently.
Attack Surface and Impact
The vulnerability exists in Chrome's libxslt code path and represents a significant security concern. While the bug allows code execution within the sandbox, a complete system compromise would likely require chaining this vulnerability with a separate sandbox escape. Google has not confirmed whether such chaining is occurring in active attacks.
CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on November 10, emphasizing the threat's severity. The bug is particularly concerning as it affects multiple Chrome channels, though Extended Stable, ChromeOS, and Android may experience delays in receiving the patch.
Broader Browser Implications
Microsoft Edge and other Chromium-based browsers are also potentially vulnerable as they share Chrome's underlying codebase. Users of these browsers should check for and install the latest security updates. The vulnerability highlights an ongoing challenge for browser security teams as use-after-free flaws continue to appear frequently in Chrome's release notes.
Google plans to remove XSLT support entirely on November 17, which will reduce the attack surface. However, until users update to Chrome 157.0.8103.50 or higher, they remain exposed to active exploitation. Security experts recommend verifying Chrome versions immediately and forcing updates if necessary.