What happened
Google issued a Chrome Stable security update on November 9 that includes nine fixes, seven rated high severity and two medium. One of the high-severity issues, CVE-2026-125350, is a use-after-free vulnerability in Chrome's XML component. Google's release notice explicitly confirms that an exploit for this specific issue exists in the wild. The company identifies the report date as November 6 but does not disclose who is exploiting it, which sites or users were targeted, or how the exploit is delivered. Independent reporting from GBHackers on November 10 corroborates the advisory and emphasizes the need to update. The fixed desktop versions are 157.0.8103.50 or .51 on Windows and macOS, and 157.0.8103.50 on Linux. Google says distribution will continue over the coming days and weeks.
Why it matters
Browsers process untrusted web content continuously, making memory-safety defects especially important to desktop and enterprise security. A use-after-free occurs when software accesses memory after it has been released; the actual consequences depend on the exploit and surrounding defenses. Google's statement establishes real-world exploitation, not a particular outcome such as full device takeover. The update also addresses other vulnerabilities in graphics, scripting and file-system components, but the advisory does not say those additional bugs are being exploited. Users and administrators should distinguish the confirmed exploited identifier from the separate XML use-after-free issue, CVE-2026-125346, in the same release.
What to watch next
Users should open Chrome's About page, allow the update to finish and relaunch the browser. Organizations should check actual installed build numbers, including machines that rarely restart, and monitor their managed rollout. Extended Stable has its own update track, so administrators must use the version appropriate to their channel rather than assuming every Chrome installation has the same number. Other Chromium-based browsers require confirmation from their respective vendors. Watch for more technical details from Google once disclosure restrictions are lifted and for any trustworthy indicators that clarify the exploitation campaign.