Quick answers
- Is CVE-2026-17727 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17727 being exploited in the wild.
- How severe is CVE-2026-17727?
- Informational severity, with a CVSS score of 8.8, published 30 July 2026.
- Which products and versions are affected?
- Google Chrome prior to 151.0.7922.72.
- Is there a fix for CVE-2026-17727?
- A patch was published on 2026-07-29: Fixed in Chrome version 151.0.7922.72 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17727 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-17727?
- 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.
Technical details
An out-of-bounds write vulnerability (CWE-787) exists in the WebGL implementation of Google Chrome on Android. The flaw is triggered when the browser processes a specially crafted HTML page, allowing a remote attacker to write data outside the intended buffer boundaries. This memory corruption can be leveraged to achieve a sandbox escape, bypassing the security boundaries that isolate the browser process from the rest of the Android operating system. The issue is resolved in version 151.0.7922.72.
Affected products
- Google Chrome prior to 151.0.7922.72
Timeline
- 2026-07-29: patched: Fixed in Chrome version 151.0.7922.72
- 2026-07-30: disclosed