Sandbox escape use-after-free in Chrome GPU

Successful exploitation could allow a remote attacker, starting from an already-compromised renderer process, to potentially escape the browser sandbox. This would let the attacker move beyond the renderer’s isolation boundary and gain broader access to the browser or underlying system context than renderer-only compromise would permit. The supplied content states there was no evidence of in-the-wild exploitation at the time of release.

Apply Google-provided updates immediately after appropriate testing. Until patching is complete, reduce exposure by enforcing least privilege, avoiding administrative browser sessions, using application isolation and exploit protections, restricting access to untrusted or risky web content, limiting unnecessary browser extensions, and using URL/DNS filtering and related web controls. Because exploitation requires crafted HTML content and a prior renderer compromise, minimizing exposure to untrusted web content may reduce risk but does not replace patching.

Upgrade Google Chrome to a fixed version. The supplied content identifies Google Chrome 150.0.7871.47 or later as fixed for the affected issue; broader release guidance in the provided advisories lists Windows and macOS 150.0.7871.46/.47 or later, Linux 150.0.7871.46 or later, and Android 150.0.7871.63. Restart the browser after updating so the new version is fully applied, and verify managed Chromium-based deployments have received corresponding vendor updates where applicable.