Chrome on Windows contains a use‑after‑free flaw in its XR subsystem. If an attacker has already compromised a renderer process, they can send a specially crafted HTML page that triggers access to freed memory, potentially escaping Chrome’s sandbox. The weakness is classified as CWE‑416 and is deemed Critical by Chromium, indicating that successful exploitation could let the attacker execute arbitrary code outside the browser context.

Google Chrome on Windows versions prior to 148.0.7778.216 are affected. Administrators should verify local installations of Chrome to ensure they are not running any earlier version of the browser.

The exploit requires the renderer process to be compromised, making it a non‑trivial remote attack that does not rely on a plain web page. No EPSS data are available and the vulnerability is not listed in the CISA KEV catalog. The CVSS score is 9.0, indicating a Critical severity. Because the flaw is in the browser’s sandbox, successful exploitation could allow an attacker to break out and potentially compromise the host system, so the risk remains high for systems still using affected Chrome versions.