ChromeWeb browser · Google
CVE-2026-17676
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 · uneditedInappropriate implementation in ANGLE in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
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 · high confidenceThis vulnerability in Google's ANGLE graphics library (used by Chrome for Android) allows an attacker who has already compromised the browser's renderer process to escape the sandbox security boundary via a specially crafted HTML page. The flaw is an implementation error rather than memory corruption, and affects Chrome Android versions prior to 151.0.7922.72.
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.
-
Confirm Google Chrome for Android is installedOpen Android Settings > Apps > Google Chrome, or check via 'adb shell pm list packages | grep chrome'Affected if Google Chrome for Android is installed on the device
-
Retrieve the installed Chrome versionNavigate to chrome://version in Chrome, or check via 'adb shell dumpsys package com.android.chrome | grep versionName'Affected if The displayed version number is visible and can be compared
-
Compare version against the affected rangeCheck if the installed version is numerically less than 151.0.7922.72 (e.g., 151.0.7922.71, 150.x.x.x, etc.)Affected if Installed version is below 151.0.7922.72 - this indicates the vulnerability is present
A user is affected if Google Chrome for Android is installed and its version is below 151.0.7922.72, since this is the only vulnerable configuration for this CVE.
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 via the Google Play Store to obtain the patched version.
Google Chrome on Android version 151.0.7922.72 or later
- Open Google Play Store on the Android device
- Search for Google Chrome or locate it in installed apps
- Ensure Chrome is updated to version 151.0.7922.72 or later
- Verify the version by navigating to chrome://version in the browser address bar
- If auto-update is enabled, confirm the update has been applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-17676 — 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-17676 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