ChromeWeb browser · Google
CVE-2026-11035
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 Custom Tabs in Google Chrome on Android prior to 149.0.7827.53 allowed a local attacker to perform privilege escalation via a crafted XML file. (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 confidenceA local privilege escalation vulnerability exists in Google Chrome for Android's Custom Tabs feature. An attacker with local access can exploit an inappropriate implementation by loading a crafted XML file to elevate privileges. The issue was patched in Chrome version 149.0.7827.53.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/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.
-
Check Google Chrome version on AndroidOpen Chrome app > tap three-dot menu > tap Settings > scroll to About Chrome; the version number is displayed under 'Chrome'Affected if Version is less than 149.0.7827.53 (for example, 149.0.7827.52 or earlier)
-
Verify Chrome is used via Custom Tabs in your appsReview your installed applications: any third-party Android app that opens web content using Chrome (typically indicated by 'Open in Chrome' or a Chrome-customized browser window) is using Custom Tabs; check app permissions for apps with WebView or browser-like behaviorAffected if Any app on the device uses Custom Tabs to display web content AND the Chrome version is vulnerable
-
Confirm Android as the target platformThis vulnerability specifically affects Android devices; verify the target device runs Android OSAffected if Device runs Android AND Chrome version is below 149.0.7827.53
A user is affected if Google Chrome on their Android device is version 149.0.7827.53 or lower and any app on that device uses Custom Tabs to load web 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.53
Update Google Chrome for Android to version 149.0.7827.53 or later. As this is a local privilege escalation, ensure devices are not left unattended or exposed to untrusted local users.
149.0.7827.53 or later
- Open Google Play Store on your Android device
- Search for 'Google Chrome' in the Play Store
- If an update is available, tap the 'Update' button to install version 149.0.7827.53 or later
- Alternatively, ensure Google Play auto-updates is enabled and wait for the update to propagate automatically
- After updating, verify the Chrome version by navigating to chrome://settings/help to confirm version 149.0.7827.53 or newer is installed
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-11035 — 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-11035 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