A type confusion flaw was found in the tab handling logic of Google Chrome on Android prior to version 151.0.7922.72. If a remote attacker can compromise the renderer process— for example by hosting a crafted HTML page— the flaw can be leveraged to escape Chrome’s isolated sandbox, potentially allowing arbitrary code execution with system privileges. The vulnerability is categorized as a medium‑severity issue by the Chromium security team. The weakness corresponds to CWE‑843, indicating improper handling of type conversions.

The affected product is Google Chrome for Android. Any installation of Chrome before version 151.0.7922.72 is susceptible. The flaw is specific to the renderer process of the mobile browser on Android devices.

The CVSS score is 5.8, reflecting a medium threat level. The EPSS score of less than 1% indicates a very low probability that the vulnerability will be exploited in the wild, and the flaw is not listed in CISA’s KEV catalog. Exploitation requires the attacker to first compromise the renderer process, a step that is non‑trivial and typically depends on other client‑side weaknesses or social engineering. Once the renderer is compromised, the attacker can trigger the type confusion to escape the sandbox and gain privileged execution on the device.