
Google Patched Chrome's Eighth Zero-Day of 2026. The "Cooling Down" Story Lasted Six Days.
CVE-2026-125350 is a libxslt use-after-free reported on Monday and patched Thursday. It's the eighth Chrome bug Google has confirmed exploited in the wild this year — and the gap pattern that looked like it was slowing down in September broke within a week.
CVE Tools4 min read
On November 9, 2026, Google shipped Chrome 157.0.8103.50 for Windows, macOS and Linux, fixing CVE-2026-125350 — a use-after-free in the XSLT pattern-matching cache that Chrome's XML engine uses. Google's own advisory language is the one line it reserves for its most urgent fixes: an exploit for this CVE "exists in the wild." CISA added it to the Known Exploited Vulnerabilities catalog the same day, with a federal remediation deadline of November 24, 2026.
Scores as of 2026-11-11live record →
What CVE-2026-125350 actually is
CVE-2026-125350 is a use-after-free (CWE-416) in the component Chrome's bug tracker labels "XML." The underlying issue sits in libxslt, the library Chrome uses to transform XML via XSLT stylesheets: a nested XML evaluation can free and replace a cached pattern-matching object while an earlier operation still holds a pointer to its old memory address, and a later double-free or use of that freed memory can be turned into arbitrary code execution inside Chrome's sandbox. An anonymous researcher reported the bug on November 6, 2026; Google tagged a fix build on November 8 and shipped it to the Stable channel as 157.0.8103.50/.51 (Windows/macOS) and 157.0.8103.50 (Linux) on November 9. The CVE record was published November 10 with a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and an SSVC exploitation status of "active." As with every entry on this list, "inside the sandbox" means this bug alone gets an attacker into Chrome's renderer sandbox — a device compromise still needs a separate sandbox-escape bug, which Google's advisory does not claim exists here.
The full 2026 tally
| CVE | Disclosed | Component | Weakness | CVSS | EPSS | Public PoC |
|---|---|---|---|---|---|---|
| CVE-2026-2441 | 2026-02-13 | CSS engine | Use-after-free | 8.8 | 54.5% | Yes (GitHub) |
| CVE-2026-3909 | 2026-03-12 | Skia (graphics) | Out-of-bounds write | 8.8 | 2.3% | No |
| CVE-2026-3910 | 2026-03-12 | V8 | Inappropriate implementation | 8.8 | 2.7% | No |
| CVE-2026-5281 | 2026-04-01 | Dawn (WebGPU) | Use-after-free | 8.8 | 13.7% | No |
| CVE-2026-11645 | 2026-06-08 | V8 | OOB read/write | 8.8 | 2.4% | No |
| CVE-2026-85046 | 2026-09-03 | V8 | Type confusion | 8.8 | 1.8% | No |
| CVE-2026-87491 | 2026-09-09 | V8 | Out-of-bounds write | 8.8 | 3.5% | No |
| CVE-2026-125350 | 2026-11-10 | XML/libxslt | Use-after-free | 8.8 | n/a (just published) | No |
The gap that broke the pattern
| Label | Value |
|---|---|
| Feb 13 → Mar 12 (2441→3909) | 27 |
| Mar 12 → Apr 1 (3910→5281) | 20 |
| Apr 1 → Jun 8 (5281→11645) | 68 |
| Jun 8 → Sep 3 (11645→85046) | 87 |
| Sep 3 → Sep 9 (85046→87491) | 6 |
| Sep 9 → Nov 10 (87491→125350) | 62 |
In September, an 87-day gap since the last confirmed zero-day — the longest stretch of 2026 — made a reasonable case that Chrome's exploited-zero-day rate was slowing down. Six days later, CVE-2026-87491 landed: the shortest gap of the entire year, immediately after the longest one. Then nothing for 62 days until CVE-2026-125350. There is no visible rhythm here — short gaps, long gaps and whiplash reversals all happened inside the same eight-month window on our own trends data. "Time since the last Chrome zero-day" is not a forecasting signal; it's a number that resets to zero on no notice.
A severity label worth noticing
CVE-2026-87491's own Chromium bug-tracker description rates it "Chromium security severity: Medium" — yet it carries the same 8.8 CVSS as every High-rated entry on this list, and CISA added it to KEV the same day it was published. Chromium's internal severity rating and the CVE's public CVSS score are produced by different processes for different audiences; a Medium internal label did not mean a lighter real-world risk or a slower KEV response. If you triage Chrome CVEs by any single score, confirm which score you're reading.
What to actually do
- Restart Chrome. The CVE-2026-125350 fix ships silently in the background but only takes effect on relaunch — a 'patched' fleet that hasn't restarted is still exploitable.
- Confirm the version: 157.0.8103.50 or later (157.0.8103.51 on the Windows/macOS build channel), via chrome://settings/help.
- Check Chromium-based browsers separately — Edge, Brave, Opera, Vivaldi take the same V8/XML fixes on their own release cadence, typically a few days behind Chrome.
- CVE-2026-125350 needs user interaction (loading a crafted page), so URL filtering and anti-phishing controls reduce exposure before every endpoint is patched — but they don't replace patching.
- If you run any of the other seven 2026 Chrome zero-days in your environment's patch history, verify the fixed version was actually deployed and the browser was restarted — not just that an update was 'available.'
Data as of 2026-11-11
Sources: Google Chrome Releases — Stable Channel Update for Desktop, Nov 9, 2026; CVE.org record for CVE-2026-125350; CISA Known Exploited Vulnerabilities catalog.