A use‑after‑free flaw exists in Chrome's DevTools that can allow a renderer process to access memory that has already been freed. This memory‑management weakness, classified as CWE‑416, may enable a remote attacker who has compromised the renderer to escape the browser sandbox. The CVE description states the escape is "potentially" achievable through a crafted HTML page, but it does not confirm that arbitrary code execution is guaranteed.

Google Chrome desktop versions prior to 148.0.7778.96 on all supported operating systems – macOS, Linux, and Windows – are affected. The stable channel built with those revisions remains vulnerable; newer releases are considered fixed.

The CVSS score of 8.3 categorises this as a high‑severity flaw, while no EPSS score is published and it is not listed in CISA's KEV catalog. Exploitation requires an attacker to compromise the renderer process first, typically by delivering malicious content within a web page. The likely attack vector is a crafted HTML page that triggers the use‑after‑free in DevTools. Given the need for an initial renderer compromise, the overall risk is moderate, but applying the patch removes the vulnerability entirely.