ChromeWeb browser · Google
CVE-2026-11119
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 GPU in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
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 confidenceInappropriate implementation in Google Chrome's GPU component on Android prior to version 149.0.7827.53 allows a remote attacker with an already compromised renderer process to potentially escape the sandbox via a crafted HTML page. The CVSS 9.6 indicates critical severity due to the sandbox escape potential.
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.
-
Identify Chrome on AndroidCheck if Google Chrome browser is installed on the Android device. Go to Settings > Apps and look for Google Chrome, or check the Chrome app icon on the device.Affected if Google Chrome is not installed on the Android device, this CVE does not apply.
-
Determine installed Chrome versionOpen Google Chrome on the Android device, tap the three-dot menu, go to Settings > Help and About Chrome. The version number will be displayed on that screen.Affected if The version shown is less than 149.0.7827.53, indicating the device is running an affected version.
-
Confirm platform is AndroidVerify that the Chrome browser in question is the Android version, not Chrome iOS, Chrome Desktop, or a Chromium-based browser. Check the app package name in Settings > Apps > Google Chrome - it should be 'com.android.chrome'.Affected if The affected product specifically targets Google Chrome on Android; other platforms are not covered by this CVE.
-
Assess attack surfaceThe vulnerability requires a compromised renderer process to exploit. Determine if the device has been exposed to risky browsing behavior, untrusted HTML content, or if the browser has been accessed by potentially malicious applications.Affected if A compromised renderer process is a precondition for this sandbox escape, making the device vulnerable only after initial compromise.
A user is affected if Google Chrome for Android is installed with a version lower than 149.0.7827.53 and the renderer process has been compromised.
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 on Android to version 149.0.7827.53 or later. Organizations should ensure mobile device management or automatic updates are enabled to deploy this patch.
Chrome for Android version 149.0.7827.53 or later
- Open Google Play Store on the Android device
- Search for "Google Chrome" or locate it in installed apps
- Tap on Chrome and select "Update" if an update is available
- Alternatively, enable automatic updates in Google Play Store settings to ensure Chrome stays current
- After updating, verify the version by navigating to chrome://version in the browser address bar
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11119 — 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-11119 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