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