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-106328 Overview
CVE-2026-106328 is an incorrect authorization vulnerability [CWE-863] in the PDF component of Google Chrome on Android. The flaw affects Chrome versions prior to 155.0.8059.39. A local attacker who convinces the user to install a malicious application can leverage a co-installed app to obtain sensitive information from Chrome's PDF handling. Google classifies the Chromium security severity as Medium. Exploitation requires social engineering and the presence of a secondary attacker-controlled app on the device.
Critical Impact
A co-installed Android app can read sensitive information handled by Chrome's PDF subsystem, bypassing expected authorization boundaries between apps.
Affected Products
- Google Chrome for Android prior to 155.0.8059.39
- Google Android (host operating system for the affected Chrome client)
- Deployments running co-installed third-party Android applications alongside Chrome
Discovery Timeline
- 2026-10-06 - CVE-2026-106328 published to NVD
- 2026-10-07 - Last updated in NVD database
Technical Details for CVE-2026-106328
Vulnerability Analysis
The vulnerability resides in Chrome's PDF handling on Android. Chrome fails to correctly enforce authorization checks when another installed application interacts with PDF-related interfaces. This classifies as an incorrect authorization weakness under [CWE-863]. The practical result is unauthorized access to sensitive PDF data that should be isolated from other apps on the device.
Exploitation is not fully autonomous. The attacker must convince the user to install or interact with a secondary application through social engineering. Once the co-installed app is in place, it can reach the exposed PDF surface in Chrome and extract information. Confidentiality is impacted; integrity and availability are not affected per the CVSS vector.
Root Cause
The root cause is missing or incorrect authorization logic in the PDF component when handling cross-application requests on Android. Chrome does not sufficiently validate the identity or entitlement of the calling app before releasing PDF content or metadata. See the Chromium Issue Tracker #518091868 for upstream details.
Attack Vector
The attack vector is network-adjacent in CVSS terms but requires a local Android device state in which a malicious app is co-installed with Chrome. The attacker delivers the secondary app through social engineering such as sideloading, a store listing, or a disguised update. After installation, the malicious app interacts with Chrome's PDF handling to retrieve sensitive information without additional user action.
No public proof-of-concept is available at the time of publication, and no exploitation in the wild has been reported. Refer to the Google Chrome Stable Update advisory for vendor commentary.
Detection Methods for CVE-2026-106328
Indicators of Compromise
- Installation of unexpected or recently sideloaded Android applications on devices running Chrome prior to 155.0.8059.39.
- Android apps requesting intents, content providers, or file access related to Chrome's PDF handling without a clear business purpose.
- Unusual inter-process communication patterns between third-party apps and the Chrome package on managed devices.
Detection Strategies
- Inventory Chrome for Android versions across managed mobile fleets and flag any installation below 155.0.8059.39.
- Review mobile threat defense telemetry for apps that query Chrome content providers or trigger PDF-related intents shortly after installation.
- Correlate app install events with subsequent cross-app data access attempts observed in Android audit logs.
Monitoring Recommendations
- Enable mobile device management (MDM) reporting of Chrome version strings and alert on outdated builds.
- Monitor enterprise app catalogs and sideload events, treating sudden installs of unknown PDF or utility apps as suspicious.
- Forward mobile endpoint and MDM logs to a centralized data lake for retrospective hunting against PDF-related IPC activity.
How to Mitigate CVE-2026-106328
Immediate Actions Required
- Update Google Chrome for Android to version 155.0.8059.39 or later on all managed and personal devices.
- Audit installed Android applications and remove any untrusted or sideloaded apps that lack a documented business need.
- Enforce MDM policies that block installation from unknown sources on corporate-managed Android devices.
Patch Information
Google fixed CVE-2026-106328 in Chrome for Android 155.0.8059.39. Patch details are published in the Google Chrome Stable Update release notes. Technical context is tracked in Chromium Issue Tracker #518091868. Administrators should push the updated Chrome build through Google Play managed updates or MDM-driven app distribution.
Workarounds
- Restrict Chrome usage for viewing sensitive PDF content on Android devices until the patched version is deployed.
- Use enterprise mobility policies to limit which third-party apps can be installed alongside Chrome.
- Educate users to avoid installing applications from untrusted sources, which is the primary precondition for exploitation.
# Example: query installed Chrome version on an Android device via adb
adb shell dumpsys package com.android.chrome | grep versionName
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

