# CVE-2026-11035: Google Chrome for Android privilege escalation in Custom Tabs

Source: https://junglewise.ai/threats/cve-2026-11035-google-chrome-for-android-privilege-escalation-in-custom-tabs  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-04. Updated: 2026-06-05  
License: CC BY 4.0 with a link back

CVE-2026-11035 · Severity: info · CVSS 0 · Published 2026-06-04

A vulnerability in Google Chrome for Android could allow a local attacker to gain elevated privileges on a device. This issue occurs within the Custom Tabs feature, which apps use to display web content. An attacker could exploit this by using a specially crafted file to bypass security boundaries, potentially compromising user data or device operations.

Technologies: [Google Chrome for Android](https://junglewise.ai/threats/technologies/chrome-for-android). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-11035 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-11035 being exploited in the wild.

**How severe is CVE-2026-11035?** Informational severity, with a CVSS score of 0, published 4 June 2026.

**Which products and versions are affected?** Google Chrome for Android prior to 149.0.7827.53.

**Is there a fix for CVE-2026-11035?** A patch was published on 2026-06-02: Chrome 149 promoted to stable channel Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-11035 attacked?** It is attacked with local access, in a network appliance.

**Am I affected by CVE-2026-11035?** Check whether you run Google Chrome for Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A privilege escalation vulnerability exists in Google Chrome for Android's Custom Tabs component due to an inappropriate implementation of input handling. The flaw, classified as improper input validation (CWE-20), allows a local attacker to trigger elevated permissions by providing a specially crafted XML file. The vulnerability was addressed in version 149.0.7827.53. While the specific mechanism of the escalation is restricted, it typically involves bypassing Android's Intent or permission model through the browser's interface with other applications.

## Affected products

- Google Chrome for Android prior to 149.0.7827.53

## Timeline

- 2026-06-02: patched: Chrome 149 promoted to stable channel
- 2026-06-04: disclosed: NVD publication date

## References

- [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html)
- [https://issues.chromium.org/issues/497936421](https://issues.chromium.org/issues/497936421)

## Related threats

- [Google Chrome WebView sandbox escape via improper input validation](https://junglewise.ai/threats/cve-2026-17741-google-chrome-webview-sandbox-escape-via-improper-input)
- [Google Chrome for Android use after free in WebView](https://junglewise.ai/threats/cve-2026-13037-google-chrome-for-android-use-after-free-in-webview)
- [Google Chrome WebView sandbox escape on Android](https://junglewise.ai/threats/cve-2026-12438-google-chrome-webview-sandbox-escape-on-android)
- [Google Chrome for Android navigation bypass in Reader Mode](https://junglewise.ai/threats/cve-2026-11297-google-chrome-for-android-navigation-bypass-in-reader-mode)
- [Google Chrome for Android use after free in Messages](https://junglewise.ai/threats/cve-2026-11163-google-chrome-for-android-use-after-free-in-messages)