A use‑after‑free flaw in Chrome’s UI side chain triggers when native objects in the renderer process are freed incorrectly, allowing a malicious page to access memory that has already been released. The attacker can then use this condition to escape the renderer sandbox via a crafted HTML page. The flaw is a classic example of CWE‑416, where a null or dangling pointer is dereferenced after free, and it also maps to CWE‑825, which denotes information exposure through unintended memory disclosure after use‑after‑free.

Google Chrome versions prior to 148.0.7778.168. Any user running a pre‑update Chrome may be vulnerable if their renderer process can be compromised by a crafted HTML page.

The CVE has a CVSS score of 8.3, indicating a high‑severity issue. EPSS data is not available and the vulnerability is not yet in the CISA KEV catalog. The exploit requires the attacker already to compromise the renderer process, after which a sandbox escape becomes possible. Attackers could deliver malicious content via a crafted HTML page served from an untrusted site. Based on the description, this is inferred because the exploit requires the attacker to compromise the renderer process and then use a crafted HTML page. The use‑after‑free flaw also falls under CWE‑825, potentially exposing sensitive data from the renderer process during the escape. The lack of an EPSS score or KEV status does not diminish the risk if the vulnerability is exploited in the wild.