Cybersecurity

Google Patches Chrome Zero-Day CVE-2026-125350 Already Exploited in the Wild

Published By Shivam Sharma4 min read
Google Chrome logo on a dark blue background, Chrome zero-day CVE-2026-125350

Google has patched Chrome zero-day CVE-2026-125350, a high-severity use-after-free flaw in Chrome’s XML component that attackers are already exploiting in the wild. It is the eighth Chrome zero-day exploited in attacks this year, according to SecurityWeek, and CISA added it to its Known Exploited Vulnerabilities catalog on 10 November, with a federal deadline of 24 November. The fix is in Chrome 157.0.8103.50 for Windows, Mac and Linux, with 157.0.8103.51 also listed for Windows and Mac.

Google’s advisory says it “is aware that an exploit for CVE-2026-125350 exists in the wild”, as quoted by CybersecurityNews. CISA’s catalog entry says the flaw “could allow a remote attacker to execute arbitrary code inside the sandbox via a specially crafted webpage”, and names Microsoft Edge and Opera among the Chromium browsers affected. Google has not said who is exploiting it, who was targeted, or how the attacks are delivered.

What Chrome zero-day CVE-2026-125350 is

CVE-2026-125350 is a use-after-free bug, CWE-416, in Chrome’s XML component. NVD scores it 8.8 out of 10 under CVSS 3.1, rated High, according to The Hacker News. The flaw sits in the libxslt code that handles XSLT, according to ThreatDefence, and Chromium’s public fix includes a test case that crashes an unpatched browser, though no working exploit has been published.

Three days from report to patch, and a 28-day shadow

An anonymous researcher reported CVE-2026-125350 on 6 November, and Google patched it on 9 November, three days later, according to CybersecurityNews. That is faster than the two earlier exploited Chrome zero-days in this comparison, which took 30 and 33 days from report to patch. CVE-2026-85046 was reported on 4 August and patched on 3 September, and CVE-2026-87491 was reported on 6 August and patched on 8 September.

There is a wrinkle. The same flaw had been reported on 12 October by Arni Hardarson of Neonix Security, under CVE-2026-125346, which ThreatDefence reports was merged into CVE-2026-125350 as a duplicate. Measured from that first report, the patch took 28 days, not three. The three-day figure is the time from the anonymous report to the patch; the 28-day figure is the time from the first report. The seven earlier exploited zero-days this year, as listed by SecurityWeek, are CVE-2026-2441, CVE-2026-3909, CVE-2026-3910, CVE-2026-5281, CVE-2026-11645, CVE-2026-85046 and CVE-2026-87491.

The patch landed six days after Chrome 157 itself launched on 3 November with 213 security fixes, including seven rated Critical. Chrome zero-day CVE-2026-125350 was reported on 6 November, three days after that launch, so it needed its own emergency follow-up build, .50 and .51, instead of the launch builds .38 and .39, our own timeline from the two release dates.

The other eight fixes in the same patch

The 9 November patch carries nine security fixes in total: seven rated High and two rated Medium, with no Critical fixes at all, our own count from Google’s severity split. The exploited flaw is the most urgent bug in a patch that contains no Critical-rated flaw, so severity alone would not have flagged it. The other eight fixes, with no exploitation reported for any of them, are:

CVE Component Flaw
CVE-2026-125345 WebGL Uninitialized resource
CVE-2026-125347 FileSystem Incorrect authorization
CVE-2026-125343 Compositing Buffer overflow
CVE-2026-125348 GPU Out-of-bounds write
CVE-2026-125344 V8 Type confusion
CVE-2026-125346 XML Use-after-free
CVE-2026-125349 GPU Uninitialized resource
CVE-2026-125342 GPU Uninitialized resource

ThreatDefence reports that CVE-2026-125346 was merged into CVE-2026-125350 as a duplicate. The table above shows the patch as Google listed it on 9 November. The nine flaws in the patch were reported over almost four months, from CVE-2026-125349 on 20 July to Chrome zero-day CVE-2026-125350 on 6 November, a span of 109 days by our own count. The zero-day was the last of the nine to be reported and the only one Google confirmed was being exploited.

CISA’s 24 November deadline

CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on 10 November 2026, with a federal civilian remediation deadline of 24 November, according to The Hacker News and confirmed by CISA’s own catalog. The entry lists ransomware use as “Unknown” and names Edge and Opera among the affected Chromium browsers. Microsoft confirmed the Edge fix on 15 November in Edge 157.0.4341.46, according to ThreatDefence.

Google is keeping the bug details and links restricted until most users have the fix, according to CybersecurityNews, and has not said who is behind the attacks or who they target. The Extended Stable channel gets the fix in version 156.0.8078.96. The SANS Internet Storm Center covered the flaw in its Stormcast episode on Tuesday 10 November.

If your browser has been sitting open for days, this is the update to restart for. Open the Chrome menu, choose Help, then About Google Chrome, and select Relaunch when it appears. You want 157.0.8103.50 for Linux, or 157.0.8103.50 or .51 for Windows and Mac, and if you update today, you get the newer 11 November build, 157.0.8103.78 for Linux and .78 or .79 for Windows and Mac, which includes this fix. Linux users should update through their package manager. ThreatDefence also reports an Android .50 build, but Google’s desktop release notice does not cover Android, so that part is unverified here. Chromium-based browsers need their own vendor patches; a Chrome update does not fix Edge or Opera.