ChromeWeb browser · Google
CVE-2026-11672
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 · uneditedHeap buffer overflow in GPU in Google Chrome on Android prior to 149.0.7827.103 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 confidenceHeap buffer overflow vulnerability in the GPU component of Google Chrome for Android before version 149.0.7827.103 allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via a specially crafted HTML page.
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
< 149.0.7827.102CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 if Google Chrome for Android is installedOpen Settings > Apps on the Android device and look for 'Chrome' in the app list, or use ADB command: pm list packages | grep chromeAffected if Chrome for Android is present on the device
-
Retrieve the installed Chrome versionOpen Chrome app, tap the three-dot menu > Help and About Chrome, or use ADB: dumpsys package com.android.chrome | grep versionNameAffected if The displayed version number is lower than 149.0.7827.102
-
Compare version against affected rangeCompare the installed version (e.g., 149.0.7827.101 or earlier) against the vulnerable threshold of 149.0.7827.102. Any version below this number is within the affected rangeAffected if Installed version is less than 149.0.7827.102 (the first digit after the decimal indicates the major version, so 149.0.7827.101 < 149.0.7827.102)
-
Confirm the GPU component is in useThis vulnerability exists in the GPU component which is active whenever Chrome renders web content. No special configuration check needed - if Chrome is installed and used, the GPU component is presentAffected if Chrome is installed and functional - the GPU component vulnerability exists in the affected versions regardless of specific settings
The device is affected if Google Chrome for Android is installed and the version number is less than 149.0.7827.102, as this is the version range containing the heap buffer overflow in the GPU component.
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 · scoped149.0.7827.102
Update Google Chrome for Android to version 149.0.7827.103 or later. For enterprise environments, deploy the update through MDM/EMM solutions and verify completion across managed devices.
Chrome for Android version 149.0.7827.103 or later
- Open the Google Play Store app on the Android device
- Search for Google Chrome
- Tap Update if an update is available, or verify the app is up to date
- Alternatively, open Chrome > tap three dots > Settings > Help & About > Google Chrome to trigger a version check and update
- Ensure automatic updates are enabled in the Google Play Store settings for Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11672 — 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-11672 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