CVE-2026-125350 - Chrome libxslt Double-Free

Started by prime2 replies32 views

CVE-2026-125350 - Chrome libxslt Double-Free / UAF (RCE Primitive)

Author: Prime
Date: Nov 2026
Target: Google Chrome x64 (Vuln Build: 157.0.8103.39)
Class: Use-After-Free -> Double-Free
Status: Actively Exploited (CISA KEV)

Intro:
Dropping the R&D for the recent Chrome libxslt bug. Google patched this in .51 and CISA added it to KEV, but the trigger for the vulnerable build is clean.

A lot of people are just crashing the renderer with the standard PoC. I spent the last few days digging into the heap mechanics on Windows 11 x64 to see if we can turn this into a controlled primitive. The sandbox is still in play, but for a renderer escape/pivot, this is solid.

The Bug:
The flaw lives in libxslt/pattern.c -> xsltTestCompMatchDirect().
It's a classic re-entrancy issue. The engine caches an xmlXPathObject, calls xmlXPathEval(), but a lazy global evaluation (xsl:number) can spawn a nested call that frees the cached object. The outer frame resumes and double-frees the stale pointer.

The Hunt (Heap Grooming):
The challenge here is reclaiming the freed 0x48 byte chunk (xmlXPathObject + heap header) before the second free hits.
If you just run the basic PoC, r9 (the register being dereferenced in xmlXPathFreeObject) points to uninitialized freelist metadata (e.g., 2f1291ffffffffff).

The Crash / Control:
When we sweep the bucket sizes, we get the deterministic crash:

(8ec.20ac): Access violation - code c0000005
chrome!sqlite3_dbdata_init+0x3119bd0:
00007ffc`83ada030 418b11 mov edx,dword ptr [r9]
r9=cfbd76ffffffffff ds:cfbd76ff`ffffffff=????????

Download From Here :
Spoiler
Hidden link: log in and reply to this thread to see it
Like1

You must log in or register to reply here.

Back to Exploits