Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106326 Overview
CVE-2026-106326 is a confused deputy vulnerability in the user interface of Google Chrome on Android prior to version 155.0.8059.39. A locally installed malicious application can leverage Chrome's UI to bypass system access restrictions and reach a privileged page. The flaw is tracked by Chromium with Medium security severity and classified under [CWE-441: Unintended Proxy or Intermediary (Confused Deputy)].
The vulnerability requires a co-installed app on the same Android device, so remote exploitation is not possible. Successful exploitation yields limited confidentiality and integrity impact without affecting availability.
Critical Impact
A co-installed Android application can abuse Chrome as a confused deputy to reach privileged in-browser pages that the app would otherwise be prevented from accessing.
Affected Products
- Google Chrome for Android prior to 155.0.8059.39
- Google Android devices with vulnerable Chrome installed
- Any Android deployment permitting co-installation of untrusted applications alongside Chrome
Discovery Timeline
- 2026-10-06 - CVE-2026-106326 published to the National Vulnerability Database
- 2026-10-07 - Last updated in the NVD database
Technical Details for CVE-2026-106326
Vulnerability Analysis
The issue is a confused deputy flaw in Chrome's Android UI layer. Chrome holds privileges to render and interact with internal pages that regular Android apps cannot reach directly. When another app invokes Chrome through standard Android inter-process channels, Chrome does not sufficiently validate whether the requested action should be exposed to that caller. The caller therefore reuses Chrome's higher privilege level to perform an action it could not perform on its own.
The practical result is that a co-installed app can cause Chrome to navigate or operate on a privileged internal page. Impact is bounded to limited data exposure and limited integrity changes within Chrome, consistent with the Medium severity rating assigned by the Chromium project.
Root Cause
The root cause is missing or insufficient origin and permission checks on an entry point in Chrome's Android UI. Chrome accepts an interaction that originated from another app and acts on it with its own authority, satisfying the definition of CWE-441. The browser serves as the intermediary that lends its privileges to a less-privileged caller.
Attack Vector
Exploitation requires local access with low privileges and no user interaction. An attacker first convinces the victim to install a malicious Android application alongside Chrome. The malicious app then issues crafted intents or UI interactions that drive Chrome to a privileged page or state. Because the attack is local and the scope is unchanged, it does not propagate to remote users.
No verified exploit code is publicly available. Technical specifics are tracked in the Chromium Issue Tracker #511745101.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-106326
Indicators of Compromise
- Android applications sending intents targeting Chrome activities with unusual URIs, including chrome:// or other internal scheme targets.
- Chrome navigation events to privileged internal pages originating immediately after a third-party app launch.
- Installation of unvetted applications on managed Android devices that also host Chrome prior to 155.0.8059.39.
Detection Strategies
- Inventory Chrome for Android versions across the mobile fleet and flag any instance below 155.0.8059.39.
- Monitor Android package install telemetry for apps that declare intents or queries involving the Chrome package com.android.chrome.
- Correlate app launch events with subsequent Chrome activity to identify programmatically driven navigation patterns.
Monitoring Recommendations
- Ingest Mobile Threat Defense (MTD) and MDM telemetry into a central analytics pipeline for Chrome version and sideload visibility.
- Alert on devices where Chrome has not updated within the vendor's standard release window after 155.0.8059.39 shipped.
- Review enterprise app allow-lists to confirm only approved applications can be installed next to Chrome on corporate devices.
How to Mitigate CVE-2026-106326
Immediate Actions Required
- Update Google Chrome on Android to version 155.0.8059.39 or later through Google Play.
- Audit managed Android devices for unapproved or sideloaded applications and remove any that are not required.
- Enforce MDM policies that restrict installation sources to Google Play and vetted enterprise stores.
Patch Information
Google addressed CVE-2026-106326 in the Chrome stable channel release documented in the Google Chrome Releases Blog. Users and administrators should ensure Chrome for Android is upgraded to at least 155.0.8059.39. Additional engineering details are tracked in Chromium Issue #511745101.
Workarounds
- Prevent installation of untrusted applications on devices where Chrome cannot be immediately updated.
- Use an alternate browser on affected devices until the Chrome update is deployed, where operationally feasible.
- Apply Android work profile separation so personal apps cannot share intents with the managed Chrome instance.
# Example: query installed Chrome version on an Android device over ADB
adb shell dumpsys package com.android.chrome | grep versionName
# Example: force-update Chrome via MDM-managed Play policy (pseudocode)
# Set managed configuration: autoUpdatePolicy = ALWAYS
# Set minimum app version for com.android.chrome = 155.0.8059.39
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

