ChromeWeb browser · Google
CVE-2026-17651
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient validation of untrusted input in Dawn in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficient validation of untrusted input in Dawn (Google's WebGPU implementation) in Chrome for Android allows a remote attacker to execute arbitrary code or escape the sandbox via a malicious HTML page. This is a client-side vulnerability affecting the browser rendering engine.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 151.0.7922.72CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the browser in useConfirm the application is Google Chrome running on Android. Check the app package name is 'com.android.chrome' or verify via Chrome's settings (chrome://version).Affected if The browser is Google Chrome on Android.
-
Check installed Chrome versionOpen Chrome on Android, navigate to chrome://version, or go to Settings > About Chrome. Note the version number displayed.Affected if The installed version is below 151.0.7922.72.
-
Verify WebGPU is accessibleWebGPU is enabled by default in affected Chrome versions. Confirm by visiting a WebGPU test page (such as webgpu.github.io/webgpu-samples) or checking chrome://gpu for WebGPU listing under 'Graphics Features'.Affected if WebGPU is enabled or accessible in the browser.
A user is affected if they are running Google Chrome on Android with a version below 151.0.7922.72 and WebGPU is enabled or accessible in their browser.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped151.0.7922.72
Update Google Chrome for Android to version 151.0.7922.72 or later. Organizations should ensure Chrome is updated across managed Android devices.
Google Chrome on Android version 151.0.7922.72
- Open Google Play Store on the Android device
- Search for "Google Chrome" in the Play Store
- If an update is available, tap the "Update" button to install version 151.0.7922.72 or later
- Alternatively, enable auto-updates for Chrome in Play Store settings to receive future security updates automatically
- After updating, verify the version by opening Chrome, tapping the three dots menu, going to Settings > About Chrome to confirm version 151.0.7922.72 or newer is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-17651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-17651 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data