Sandbox Escape in Google Chrome Codecs

Successful exploitation could allow an attacker who already achieved code execution or equivalent control within the Chrome renderer process to escape the browser sandbox on Windows. This can bypass a key security boundary and enable broader access to the underlying system than would normally be available to renderer-confined code. In practical attack chains, this materially increases the likelihood of full browser compromise and may facilitate follow-on actions such as arbitrary code execution in a less restricted context, access to sensitive data, or further system compromise.

Until patched, reduce exposure by limiting use of untrusted web content, applying browser hardening controls, and restricting execution contexts that could deliver malicious HTML. Enterprise defenders can reduce risk through application isolation, least-privilege endpoint configurations, and rapid deployment of browser updates. Because the vulnerability requires prior renderer compromise, mitigations that reduce the likelihood of initial renderer exploitation also lower overall risk, but they do not replace patching.

Upgrade Google Chrome on Windows to version 150.0.7871.115 or later. Where Chromium is consumed through downstream distributions, apply the vendor-provided fixed package versions corresponding to the Chrome 150 security update. Standard patch management should prioritize this issue because it affects a sandbox boundary and is suitable for chaining with renderer compromise.