# CVE-2026-93372: Google Chrome buffer overflow in WebGL

Source: https://junglewise.ai/threats/cve-2026-93372-google-chrome-buffer-overflow-in-webgl  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-17. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-93372 · Severity: critical · CVSS 9.6 · Published 2026-09-17

Google Chrome's WebGL graphics engine contains a buffer overflow vulnerability that allows attackers to execute arbitrary code outside the browser sandbox by tricking users into viewing a malicious webpage. This type of attack can lead to complete compromise of the affected device, including theft of data and installation of malware, with no user awareness beyond visiting a link.

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

## Quick answers

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

**How severe is CVE-2026-93372?** Critical severity, with a CVSS score of 9.6, published 17 September 2026.

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

**Is there a fix for CVE-2026-93372?** A patch was published on 2026-09-17: Version 153.0.8010.52 and later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-93372?** Check whether you run Google Android or 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.

## Technical details

The vulnerability is a buffer overflow in the WebGL graphics rendering component of Google Chrome on Android. The flaw allows a remote attacker to trigger memory corruption by crafting a malicious HTML page that exploits improper bounds checking in WebGL operations. No authentication or user interaction beyond viewing the page is required; the attack is triggered automatically when the page loads. Successful exploitation results in arbitrary code execution outside the Chrome sandbox, granting the attacker full device-level access. The vulnerability was patched in Chrome version 153.0.8010.52 released on September 17, 2026.

## Affected products

- Google Chrome prior to 153.0.8010.52 on Android

## Timeline

- 2026-09-17: disclosed
- 2026-09-17: patched: Version 153.0.8010.52 and later

## References

- [https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0194356994.html](https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0194356994.html)
- [https://issues.chromium.org/issues/548085797](https://issues.chromium.org/issues/548085797)

## 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)