Intel Hub

Threat intel

Chrome gets its eighth exploited zero-day of 2026.

Google patched CVE-2026-125350, a use-after-free bug with an exploit in the wild, in Chrome 157.0.8103.50/.51. Nine flaws were fixed in the update.

Google released Chrome 157.0.8103.50/.51 for Windows and Mac, and 157.0.8103.50 for Linux, to fix CVE-2026-125350. Google says it is aware that an exploit for the flaw exists in the wild. Security Affairs reported the fix on November 10, 2026.


It is the eighth actively exploited Chrome zero-day Google has patched this year. The update fixes nine flaws in total.


Security Affairs describes CVE-2026-125350 as a use-after-free memory corruption bug. The report was submitted anonymously on November 6, 2026. Public sources disagree on the affected component: one summary points to V8, while the article body lists XML. Google has not named the component in detail.


Google has not said who is exploiting the flaw, how, or against whom. Until it does, treat it as targeted but unattributed. Restricting disclosure while patches roll out is standard practice for Chrome zero-days.


Why it matters: Chrome's update channel is the only fix. Browser memory-corruption bugs are routinely chained with sandbox escapes, so a renderer bug can become code execution on the endpoint. Chromium-based browsers such as Edge, Brave and Opera typically follow with their own builds.


What to do. Confirm managed fleets are on Chrome 157.0.8103.50 or later, and force a relaunch rather than waiting for users to restart. Check Chromium-based browsers for their matching updates. Blue teams should hunt for anomalous child processes spawned by browser processes and for unexpected crashes in the days before patching. Where possible, keep site isolation enabled and limit browsing from privileged admin accounts.

Sign-in required.

The full encrypted event log and the mitigation steps are available after sign-in.