ChromeWeb browser · Google
CVE-2026-10892
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 · uneditedOut of bounds write in GPU in Google Chrome on Android prior to 149.0.7827.53 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 · high confidenceAn out-of-bounds write vulnerability exists in the GPU component of Google Chrome on Android versions prior to 149.0.7827.53. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, potentially allowing sandbox escape and arbitrary code execution. The vulnerability has a CVSS 9.6 (Critical) rating due to the potential for complete system compromise.
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.53CVSS 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 installedOn the Android device, go to Settings > Apps and search for 'Chrome' or 'Google Chrome', or use ADB command: adb shell pm list packages | grep com.android.chromeAffected if The package com.android.chrome is present on the device
-
Determine the installed Chrome versionOpen Chrome app, tap the three-dot menu, go to Settings > About Chrome to view the version number, or use ADB: adb shell dumpsys package com.android.chrome | grep versionNameAffected if A version number is returned showing the currently installed build
-
Compare against affected version rangeCompare the installed version to the affected threshold: versions prior to 149.0.7827.53 are vulnerable. Note that version numbers follow the format major.build (e.g., 148.0.7827.52 is vulnerable, 149.0.7827.53 is patched)Affected if Installed version is less than 149.0.7827.53 (for example, 148.x.x.x or earlier)
A user is affected if Google Chrome for Android is installed and its version number is lower than 149.0.7827.53, meaning the GPU rendering component contains the unpatched out-of-bounds write vulnerability.
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.53
Update Google Chrome for Android to version 149.0.7827.53 or later. In enterprise environments, use mobile device management (MDM) tools to verify and enforce the update across all managed Android devices.
Chrome Android 149.0.7827.53 or later
- Open the Google Play Store on the Android device
- Search for "Google Chrome" or locate it in your installed apps
- Tap "Update" to install the latest version of Chrome
- Ensure the updated version is 149.0.7827.53 or later
- Restart Chrome after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10892 — 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-10892 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