ChromeWeb browser · Google
CVE-2026-12028
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 · uneditedUse after free in GPU in Google Chrome on Android prior to 149.0.7827.115 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 confidenceA use-after-free vulnerability exists in the GPU component of Google Chrome on Android devices before version 149.0.7827.115. An attacker who has already compromised the renderer process can exploit this memory corruption issue via a crafted HTML page to potentially escape Chrome's sandbox and execute code at higher privilege levels.
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.115CVSS 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 the Chrome browser version on AndroidOpen Chrome on the Android device, tap the three-dot menu, go to Settings > About Chrome to view the current version numberAffected if The displayed version is lower than 149.0.7827.115
-
Confirm the operating system is AndroidVerify the device is running Android OS (this vulnerability specifically affects Chrome on Android, not iOS or other platforms)Affected if The device runs Android OS with an affected Chrome version
-
Check if GPU rendering is activeIn Chrome on Android, go to Settings > Advanced > Graphics and verify Hardware acceleration or GPU rendering is enabled (this is typically enabled by default)Affected if GPU rendering is enabled and the Chrome version is below 149.0.7827.115 on Android
-
Verify renderer process accessThis vulnerability requires a compromised renderer process; assess whether the device has been exposed to untrusted web content or malicious HTML filesAffected if The device has been used to browse untrusted websites or open untrusted HTML content with an affected Chrome version on Android
A user is affected if Chrome on their Android device is version 149.0.7827.115 or lower and they have potential exposure to malicious HTML content.
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.115
Update Google Chrome for Android to version 149.0.7827.115 or later. Organizations should ensure mobile device management (MDM) policies enforce automatic Chrome updates or verify end-users have updated their browsers.
Chrome for Android 149.0.7827.115 or later
- Open the Google Play Store app on your Android device
- Search for "Google Chrome" or "Chrome"
- Tap on Chrome from the search results
- If an update is available, tap the "Update" button
- Alternatively, enable auto-updates by going to Play Store > Profile icon > Settings > Network preferences > Auto-update apps
- After updating, verify the version by going to Chrome > Settings > About Chrome - it should show 149.0.7827.115 or higher
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-12028 — 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-12028 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