# Chrome's eighth exploited zero-day of 2026 is an XML use-after-free. Update to 157.0.8103.50 now

> Google has shipped Chrome 157.0.8103.50/.51 to fix nine security bugs, including CVE-2026-125350, a high-severity use-after-free in Chrome's XML code that Google says is already being exploited. It's the eighth Chrome zero-day patched this year; relaunching the browser is all it takes.

Published Nov 10, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/chrome-157-cve-2026-125350-xml-zero-day-exploited-eighth-of-2026-update-now

**Google has patched an actively exploited zero-day in Chrome.** The desktop stable update released on **Monday, November 9** moves Chrome to **157.0.8103.50/.51 on Windows and Mac and 157.0.8103.50 on Linux**, and fixes nine security bugs. One of them, **CVE-2026-125350**, a high-severity **use-after-free in Chrome's XML component**, is already in attackers' hands: Google's release note says it is aware that an exploit for it "exists in the wild."

Why it matters: use-after-free bugs in a browser are a classic route to running code when someone simply opens a malicious page. The Hacker News counts this as the **eighth exploited Chrome zero-day of 2026**, so the window between disclosure and patching keeps mattering. Google hasn't said who is using it or against whom.

## What's in the update

Google's release note lists nine fixes. The exploited bug was reported anonymously; The Hacker News says the report came in on **November 6**, three days before the fix shipped.

| CVE | Severity | Component | Bug type | Credited to |
|---|---|---|---|---|
| **CVE-2026-125350** | High | XML | Use after free (**exploited**) | Anonymous |
| CVE-2026-125346 | High | XML | Use after free | Arni Hardarson (Neonix Security) |
| CVE-2026-125344 | High | V8 | Type confusion | Google |
| CVE-2026-125343 | High | Compositing | Buffer overflow | Google |
| CVE-2026-125348 | High | GPU | Out-of-bounds write | Google |
| CVE-2026-125345 | High | WebGL | Uninitialized resource | Google |
| CVE-2026-125347 | High | FileSystem | Incorrect authorization | Google |
| CVE-2026-125349 | Medium | GPU | Uninitialized resource | Google |
| CVE-2026-125342 | Medium | GPU | Uninitialized resource | Vo Duc Thang |

As usual, Google is keeping bug details restricted until most users have updated, according to The Hacker News, so there's no public write-up of how the XML flaw is triggered.

## What to do

1. **Update Chrome now.** Open the menu, go to **Help → About Google Chrome**, let it download, then click **Relaunch**. Chrome only applies the fix after a restart, so a browser left open for days is still exposed.
2. **Check the version reads 157.0.8103.50 or later** (.51 is also a fixed build on Windows and Mac).
3. **Other Chromium browsers** (Microsoft Edge, Brave, Opera, Vivaldi) share the same engine. The Hacker News advises applying their fixes as soon as each vendor ships them; check each browser's About page over the next few days.
4. **IT admins:** push the update through your management tools and force a relaunch rather than waiting for users to restart.

## What to watch

Whether CISA adds CVE-2026-125350 to its Known Exploited Vulnerabilities list, which would set a patch deadline for US federal agencies, and whether Google or a researcher links the exploit to a known spyware or espionage campaign.


## Sources

1. [Google Chrome Releases — Stable Channel Update for Desktop (November 9, 2026)](https://chromereleases.googleblog.com/2026/?hl=en)
2. [The Hacker News — Google issues Chrome security update for eighth actively exploited zero-day of 2026](https://thehackernews.com/2026/11/google-issues-chrome-security-update.html)
