# CVE-2026-17651: Google Chrome Dawn insufficient input validation sandbox escape

Source: https://junglewise.ai/threats/cve-2026-17651-google-chrome-dawn-insufficient-input-validation-sandbox-escape  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-30. Updated: 2026-07-30  
License: CC BY 4.0 with a link back

CVE-2026-17651 · Severity: info · CVSS 10 · Published 2026-07-30

Google Chrome on Android contains a critical security vulnerability in Dawn, a component used for processing web graphics. A remote attacker can exploit this flaw by tricking a user into visiting a specially crafted website. Successful exploitation could allow the attacker to break out of the browser's security sandbox, potentially gaining unauthorized access to the underlying mobile operating system and user data.

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

## Quick answers

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

**How severe is CVE-2026-17651?** Informational severity, with a CVSS score of 10, 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-17651?** A patch was published on 2026-07-29: Fixed in Stable Channel Update 151.0.7922.72 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-17651 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-17651?** 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

A critical vulnerability exists in the Dawn component of Google Chrome for Android due to improper input validation (CWE-20). The flaw is triggered when the browser processes untrusted input from a malicious web page. A remote, unauthenticated attacker can exploit this by hosting a crafted HTML page that, when visited, allows for a sandbox escape. This bypasses the primary security boundary of the browser, potentially leading to remote code execution with the privileges of the browser process or higher. Google has addressed this issue in version 151.0.7922.72.

## Affected products

- Google Chrome prior to 151.0.7922.72

## Timeline

- 2026-05-28: disclosed: Reported by Google internal researchers
- 2026-07-29: patched: Fixed in Stable Channel Update 151.0.7922.72
- 2026-07-30: advisory

## References

- [https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html](https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html)
- [https://issues.chromium.org/issues/517307966](https://issues.chromium.org/issues/517307966)

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