What is the CVSS score of CVE-2026-11035?

CVE-2026-11035 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Google Chrome are affected by CVE-2026-11035?

Google Chrome for Android versions prior to 149.0.7827.53 contain a privilege escalation vulnerability in the Custom Tabs component that could allow an attacker with device access to elevate their…. A patch is available.

How to fix or mitigate CVE-2026-11035?

Within 24 hours: Verify Chrome for Android version distribution across managed and BYOD device inventory. Within 7 days: Deploy Chrome 149.0.7827.53 or later to all managed Android devices and distribute patch guidance to end users. Within 30 days: Confirm 95%+ patch deployment across organizational Chrome for Android installations and document completion in vulnerability management system.

Google Chrome CVE-2026-11035

EUVD-2026-34484 HIGH

Improper Input Validation (CWE-20)

2026-06-04 chrome-cve-admin@google.com

GHSA-2wp5-pmpm-74rh

Privilege Escalation Google

7.3

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

7.3 HIGH

AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

SUSE

HIGH

qualitative

Red Hat

7.1 MEDIUM

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 20:25 vuln.today

CVSS changed

Jun 05, 2026 - 20:22 NVD

7.3 (HIGH)

CVE Published

Jun 04, 2026 - 23:17 nvd

HIGH 7.3

CVE Published

Jun 04, 2026 - 23:17 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

Inappropriate 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)

AnalysisAI

Local privilege escalation in Google Chrome for Android prior to 149.0.7827.53 stems from an inappropriate implementation in the Custom Tabs component, where a crafted XML file processed by a local attacker can elevate privileges within the browser context. The flaw is rated CVSS 7.3 (Chromium severity Medium) and requires user interaction, with no public exploit identified at time of analysis and a very low EPSS score (0.02%, 4th percentile). A vendor patch is available in the Stable channel update referenced by the Chrome Releases advisory.

Technical ContextAI

Chrome Custom Tabs is an Android-specific browser surface that lets third-party apps embed a customized Chrome browsing experience while sharing the user's Chrome profile, cookies, and saved state. Per CWE-20 (Improper Input Validation), the underlying defect lies in how the Custom Tabs implementation parses or trusts attacker-controlled XML input - likely an Intent extra or resource file passed from a co-resident Android application - without sufficient validation, enabling the caller to influence behavior that should be restricted to Chrome's own privilege boundary. Because Android isolates apps via UIDs, a successful exploit lets a lower-privileged app cross into actions normally reserved for the Chrome app itself.

RemediationAI

Vendor-released patch: Chrome for Android 149.0.7827.53 - update via Google Play Store or enterprise mobile device management to this version or later, per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html and Chromium issue tracker entry https://issues.chromium.org/issues/497936421. As compensating controls until the update is rolled out, restrict installation of untrusted third-party apps (since the attack requires a malicious local app to deliver the crafted XML), disable 'Install from Unknown Sources' on managed devices via MDM policy, and consider temporarily disabling Custom Tabs integrations in security-sensitive enterprise apps if feasible - though this will break in-app browsing experiences that rely on the Custom Tabs API.