Incident sheet · /security

Filed
Read
3 min · 607 words
Severity
Routine

Google Patches Eighth Actively Exploited Chrome Zero-Day of 2026

Google shipped emergency fixes for CVE-2026-125350, a use-after-free flaw in Chrome's XML parser exploited in the wild — the browser's eighth zero-day of 2026.

Google patches eighth Chrome zero-day exploited in attacks this year
FeedGoogle patches eighth Chrome zero-day exploited in attacks this year — Bernd 📷 Dittrich / unsplash

Event log

  1. Google patched CVE-2026-125350, its eighth actively exploited Chrome zero-day of 2026, via a Monday security advisory.
  2. The flaw is a high-severity use-after-free in Chrome's XML component, enabling malicious code execution.
  3. Fixed versions: Chrome 157.0.8103.50/.51 for Windows and macOS, 157.0.8103.50 for Linux.
  4. V8 engine bugs account for four of the eight 2026 Chrome zero-days; Google fixed eight more in 2025.
  5. Bug details remain restricted until most users are updated, possibly due to third-party library exposure.

Google has patched its eighth actively exploited Chrome zero-day of 2026, releasing emergency updates on Monday for a high-severity memory corruption flaw tracked as CVE-2026-125350. The bug sits in the browser's XML component and attackers are already using it.

"Google is aware that an exploit for CVE-2026-125350 exists in the wild," the company said in its Monday security advisory. That single sentence is, as usual, all the detail Google is willing to give for now.

What exactly is broken?

The flaw is a Use-After-Free (UAF) weakness in Chrome's XML component. It triggers when the browser's XML parser processes data, deletes an object from memory, but fails to clear the pointer referencing that object.

When Chrome later tries to use or read that freed memory space, an attacker can manipulate the memory layout and execute malicious code. In plain terms: browse to the wrong page with an unpatched browser, and the page runs code of someone else's choosing.

Google has found evidence of in-the-wild exploitation but has not shared additional details about the incidents. "Access to bug details and links may be kept restricted until a majority of users are updated with a fix," the company noted. It will also keep restrictions in place if the bug exists in a third-party library that other projects depend on but have not yet fixed — a hint that other browsers and software may share exposure.

Which versions fix it?

The fix is live in the Stable Desktop channel:

  • Windows and macOS: Chrome 157.0.8103.50/.51
  • Linux: Chrome 157.0.8103.50

Google warns the rollout could take days or weeks to reach everyone. BleepingComputer found the update available immediately when checking manually. Chrome also checks for updates on its own and installs them after the next launch, so most fleets will converge without admin action — eventually.

What does this change for enterprise patching?

Not much in mechanics, plenty in arithmetic. This is the eighth exploited-in-the-wild Chrome flaw since January, and CISOs running Chrome-dependent web apps or VDI estates should treat the browser as a monthly patch surface, not a set-and-forget install.

The 2026 ledger so far:

  • CVE-2026-2441 (February): iterator invalidation bug in CSSFontFeatureValuesMap, Chrome's implementation of CSS font feature values.
  • CVE-2026-3909 (March): out-of-bounds write in the Skia 2D graphics library.
  • CVE-2026-3910 (March): inappropriate implementation flaw in the V8 JavaScript and WebAssembly engine.
  • CVE-2026-5281 (April): use-after-free in Dawn, the cross-platform implementation of the WebGPU standard used by the Chromium project.
  • CVE-2026-11645 (June): out-of-bounds read and write in V8, exploited in the wild.
  • CVE-2026-87491 and CVE-2026-85046 (September): out-of-bounds write and type confusion, both in V8.

V8 accounts for four of the eight. The JavaScript engine remains Chrome's most productive attack surface, and that pattern has now held across two years: Google fixed eight more exploited zero-days in 2025.

Many of those 2025 bugs were reported by Google's Threat Analysis Group, which tracks zero-day exploits used in spyware attacks. Commercial surveillance vendors, not opportunistic criminals, have driven much of this activity — which raises the odds that this week's bug has a narrow, targeted victim set rather than a mass campaign behind it.

The practical move is simple. Force the update, confirm the build numbers, and check whether any third-party Chromium derivatives in the estate inherit the XML bug. Google's silence on shared-library exposure is a hint worth acting on.

via bleepingcomputer.com (Source)

Filed under

  • google-chrome
  • cve-125350
  • zero-day-exploits
  • browser-security
  • patch-management
Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Market editor covering people, launches and day-to-day practice in enterprise information technology and the leaders who run at CIO Monitor.

185 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›