Sandbox escape out-of-bounds write in Google Chrome ANGLE

Successful exploitation can allow an attacker to break out of the renderer sandbox, defeating a core browser security boundary. Because the flaw is an out-of-bounds write, exploitation may provide memory corruption capabilities that can be used to alter control flow or corrupt adjacent data structures in a more privileged process context. In practical terms, this can enable escalation from renderer compromise to broader code execution outside the sandbox, increased access to host resources, and follow-on actions such as persistence, lateral movement, or further privilege escalation depending on the surrounding environment.

If immediate patching is not possible, reduce exposure by limiting use of untrusted web content, isolating high-risk browsing activity, and enforcing application isolation controls around browser use. Enterprise defenders can prioritize containment of renderer-compromise scenarios by hardening endpoint protections, restricting local privilege escalation paths, and monitoring for anomalous browser child-process behavior. These measures are only temporary risk reductions and do not replace installing the vendor fix.

Upgrade Google Chrome to version 150.0.7871.182 or later. Organizations using Chromium-based browsers should also apply the corresponding vendor updates once available. Ensure the browser is fully restarted after updating so the patched binaries are loaded.