# CVE-2026-120931: Google Chrome out-of-bounds write in WebGL on Android

Source: https://junglewise.ai/threats/cve-2026-120931-out-of-bounds-write-in-webgl-in-google-chrome-on-on-android  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-120931 · Severity: critical · CVSS 9.6 · Published 2026-11-03

Google Chrome on Android contains a memory corruption flaw in its WebGL graphics renderer that allows arbitrary code execution outside the browser sandbox. An attacker can exploit this by hosting a malicious webpage, gaining complete control over the device when a user visits the site. This vulnerability can lead to data theft, malware installation, or device compromise.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-120931 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-120931 being exploited in the wild.

**How severe is CVE-2026-120931?** Critical severity, with a CVSS score of 9.6, published 3 November 2026.

**Which products and versions are affected?** Google Chrome prior to 156.0.8078.47 on Android.

**Is there a fix for CVE-2026-120931?** Yes: fixed in Chrome 156.0.8078.47 and later on Android. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-120931 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-120931?** Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Chrome 156.0.8078.47 and later on Android

## Technical details

An out-of-bounds write vulnerability in the WebGL component of Google Chrome allows remote code execution outside the sandbox via a crafted HTML page. The vulnerability affects Chrome on Android prior to version 156.0.8078.47 and requires only network access and user interaction (visiting a malicious page). Successful exploitation grants arbitrary code execution with the privileges of the Chrome process, potentially compromising the entire device.

## Affected products

- Google Chrome prior to 156.0.8078.47 on Android

## Timeline

- 2026-11-03: disclosed

## References

- [https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html](https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html)
- [https://issues.chromium.org/issues/550607402](https://issues.chromium.org/issues/550607402)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)