Chrome Zero-Day CVE-2026-125350 Lands on CISA's KEV — Google's Eighth Actively Exploited Flaw of 2026
Chrome Zero-Day CVE-2026-125350 Lands on CISA's KEV — Google's Eighth Actively Exploited Flaw of 2026
Google's zero-day count for 2026 has hit eight. On November 9, the Chrome team shipped a stable channel update fixing nine security flaws — among them CVE-2026-125350, a use-after-free in the XML component reported by an anonymous researcher on November 6. The critical detail sits in one line of the advisory: "Google is aware that an exploit for CVE-2026-125350 exists in the wild." Within a day, CISA added the flaw to its Known Exploited Vulnerabilities catalog (November 10), giving Federal Civilian Executive Branch agencies — and every organization that follows the KEV as a patch floor — until November 24 to remediate.
Use-after-free bugs are the workhorse of modern browser exploitation: when an application keeps a pointer to memory it has already released, an attacker who can groom the heap to reclaim that memory gets their data read or executed in the program's context — and in a browser, that means potential arbitrary code execution from simply visiting a malicious page. Google hasn't shared details about how CVE-2026-125350 is being exploited or who is behind the attacks, and its standard restriction note applies: bug details and links stay limited until a majority of users are running a fixed build. What is known is the fix itself — Chrome 157.0.8103.50 for Windows, Mac and Linux (with .51 rolling out for Windows and Mac) — and that it patches eight other flaws too, including High-severity ones in V8, WebGL, GPU, Compositing and FileSystem.
The pace is the story. CVE-2026-125350 is the eighth actively exploited Chrome zero-day of 2026, continuing a drumbeat that has included a CSS use-after-free (CVE-2026-2441, February), the Skia out-of-bounds write and V8 flaw pair (March), Dawn's WebGPU use-after-free (April), V8's out-of-bounds access (June), September's V8 type confusion (CVE-2026-85046 — which we covered when it landed), and another V8 out-of-bounds write later that month. Browsers remain the single most-attacked piece of software on the endpoint, and the KEV listing confirms attackers aren't waiting for users to update before firing whatever they have.
What Should You Do?
- Update Chrome now to 157.0.8103.50/.51 on Windows and Mac and 157.0.8103.50 on Linux — Help → About Chrome forces the update past the staged rollout if it hasn't reached your fleet yet.
- Extend the fix to the family: Edge, Brave, Vivaldi, Opera and other Chromium-based browsers inherit the vulnerable XML code — make sure they update alongside Chrome, they don't all auto-update on Google's schedule.
- Treat November 24 as your deadline even if you're not federal — the KEV calendar is a reasonable patch SLA for any fleet, and an actively exploited browser flaw is about the clearest high-priority patch that exists.
- Watch server-side Chromium too: embedded headless Chrome in PDF generators, scrapers and automation often runs unmanaged — inventory where a Chromium engine sits in your stack so it isn't forgotten when the desktop browsers update.
The WAF Angle
A browser zero-day is an endpoint problem, but the delivery path is usually yours: the exploit arrives via a malicious page the user visits — sometimes a compromised legitimate site. That doesn't mean a WAF can patch Chrome, but it does mean your web perimeter sees the delivery attempts: injected script tags in defaced pages, redirect chains to known exploit-kit infrastructure, and anomalous outbound traffic from "trusted" marketing pixels. The same server-side request inspection that powers your WAF rules feeds the detection story here — if your site gets compromised and becomes a zero-day delivery host, rate limiting, output sanitization and integrity monitoring are what keep you from being part of the kill chain for someone else's endpoint fleet. We noted the same delivery asymmetry when covering September's V8 type confusion CVE-2026-85046: defenders control the servers, attackers control the browsers — patch both sides of that handshake.