$RodHat_/search
MOTD

Chrome CVE-2026-125350: XML use-after-free, eighth zero-day of 2026

Published by

This article may contain Amazon affiliate links. I may earn a commission if you buy through them. Disclosure.

Editorial card for a Chrome XML use-after-free zero-day
Editorial card: RodHat

Google shipped Chrome 157.0.8103.50 for Linux on Monday to fix CVE-2026-125350, a use-after-free in the XML code. Google says an exploit exists in the wild. That is the eighth Chrome zero-day patched this year, per BleepingComputer’s count.

NVD lists it as: use after free in XML, remote attacker, “arbitrary code inside the sandbox via a crafted HTML page.” Chromium severity High, CVSS 8.8 (AV:N/AC:L/PR:N/UI:R). You have to visit the page. That is the entire barrier to entry, and it’s the thing browsers exist to do.

A use-after-free is the oldest trick in the C and C++ book. The parser frees an object, forgets to clear the pointer, and later something dereferences the dangling pointer. If the attacker arranged for the freed chunk to be reallocated with their own data, they decide what the stale pointer points at. I was reading about this class of bug when dial-up was still a personality. We keep rebuilding the same hole in new components and calling each one a surprise.

Note “inside the sandbox.” The renderer sandbox is the real engineering achievement here, and it’s why this one alone doesn’t hand over your machine. Exploit chains pair a renderer bug like this with a sandbox escape. Google has shared nothing about the in-the-wild incidents and says bug details may stay restricted until most users are updated. So I can’t tell you what the second half of the chain was, and neither can anyone quoting a press release.

For the tally, BleepingComputer lists the earlier ones: CVE-2026-2441 in February, CVE-2026-3909 and CVE-2026-3910 in March, CVE-2026-5281 in April, CVE-2026-11645 in June, CVE-2026-87491 and CVE-2026-85046 in September. Skia, V8, Dawn, CSS font feature values, and now XML. Every one is a memory-safety bug in a big pile of native code. Nobody’s lazy. The language just lets you do this.

What to do:

  1. Update. Windows and macOS get 157.0.8103.50/.51, Linux gets 157.0.8103.50. Google says rollout can take days or weeks, so don’t wait for it. Open chrome://settings/help and let it check, then restart. The update doesn’t count until the relaunch.
  2. If you run Chromium on a distro, check your package manager for the rebuilt version instead of assuming the browser self-updates. Distro builds track upstream on their own schedule, and that gap is exactly where exploits live.
  3. Chromium-based browsers such as Edge, Brave and Opera ship their own builds off the same engine. Expect their updates to follow; I haven’t seen their advisories, so look.
  4. Locked-down fleet? Push the version through your management tooling and verify with an inventory query rather than trusting “auto-update is on.”

The sandbox is the reason I’m not screaming. The pattern is the reason I’m not relaxed. For how process isolation actually works under the hood, see the Linux sandboxing hub, and for the previous Chrome fix cycle, Chrome 157 and the ANGLE bug. More security notes in the kernel and security hub. Go restart your browser.

Sources

  1. CVE-2026-125350 (NIST National Vulnerability Database)
  2. Stable Channel Update for Desktop (Chrome Releases)
  3. Google patches eighth Chrome zero-day exploited in attacks this year (BleepingComputer)