Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious co-installed Android app
-
ExploitInvoke Chrome via confused-deputy UI path
-
ExecutionBypass system access restrictions
-
ImpactReach privileged internal page
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service Proxy/intermediary controls
|
| Exploitation Conditions | Exploitation requires a malicious co-installed application already present on the same Android device; that app acts as the confused deputy to make Chrome bypass system access restrictions and reach a privileged page. Limiting factors: the attack is local-only (AV:L) with no remote or network component, it depends on the attacker first getting their app installed on the victim's device (sideloading or a trojanized app), it is specific to Chrome on Android below version 155.0.8059.39, and impact is limited to partial confidentiality and integrity with no availability loss. No end-user interaction with Chrome itself (UI:N) is required once the malicious app is in place. |
| Impact | This is a genuinely low-to-moderate, local-only issue, not an urgent priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, base 4.4, Chromium-rated Medium) describes a local attack requiring an attacker-controlled app already present on the device, delivering only partial (Low) confidentiality and integrity impact and no availability impact. EPSS reinforces low real-world risk at 0.11% (1st percentile). There is no CISA KEV listing and no public exploit identified, so the signals are consistent - low probability, low impact, no known exploitation. No SSVC decision data was provided in the input. The main caveat is the Low PR rating: the described prerequisite - a malicious co-installed Android app acting as the confused deputy - is a meaningful barrier that is arguably better captured than a raw score suggests, since the attacker must first get their app onto the target device. All signals point the same direction, so there is no contradiction to flag beyond that nuance. |
| Exploit ScenarioDerived | A user is tricked into installing a seemingly benign Android app from sideloading or a store. That co-installed app abuses Chrome's UI confused-deputy flaw to have Chrome navigate to or act on a privileged internal page on its behalf, bypassing the system access restrictions that would normally block the app. No public exploit code was identified at time of analysis, and exploitation is local-only with no remote vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Authentication and access-control bypass in Google Chrome on Android before version 155.0.8059.39 lets a malicious app already installed on the same device act as a confused deputy, driving Chrome's UI into a privileged page and circumventing system access restrictions. The flaw is local-only (AV:L) and requires the attacker to first get their app onto the victim's device via sideloading or a trojanized application, after which no further interaction with Chrome is needed (UI:N); impact is limited to partial confidentiality and integrity loss with no availability impact (CVSS 4.4). There is confirmed vendor patching but no public exploit identified at time of analysis and no CISA KEV listing, and EPSS is negligible (0.11%, 1st percentile), ranking this as a low-to-moderate, local-only issue rather than an urgent priority.
RemediationAI
Upgrade Google Chrome on Android to 155.0.8059.39 or later - Vendor-released patch: 155.0.8059.39 - distributed through the Google Play Store and referenced in the stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html. Because exploitation requires a malicious co-installed application already resident on the device, the practical compensating controls target that precondition: enforce Android Enterprise / MDM policies that disable installation from unknown sources and pin an app allowlist, which blocks sideloaded or trojanized apps (trade-off: users lose the ability to install legitimate off-store apps); and, in high-assurance environments, isolate Chrome in a work profile with restricted app-sharing so untrusted personal apps cannot invoke it (trade-off: reduced cross-profile convenience and possible breakage of app-linking flows). Users who cannot patch immediately should review installed applications and remove anything untrusted, since the confused-deputy call originates from that co-installed app; none of these workarounds fully substitute for reaching build 155.0.8059.39, since the bypass itself is fixed only by the update.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-441 (Confused Deputy): Chrome's UI layer on Android is a more privileged component that can be induced to perform operations it would not normally permit, because it fails to properly validate the authority of the requesting party. Here the requesting party is a co-installed Android application, which uses inter-process communication or intent-based entry points to cause Chrome to navigate into a privileged page, effectively borrowing Chrome's elevated context to cross a system access boundary. The CVSS vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N confirms the prerequisites: local access, low privileges for the invoking app, no user interaction with the target application, and scope unchanged - meaning the compromise stays within Chrome's security context and produces only partial confidentiality and integrity effects. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covers the Chrome product family, with the Android build prior to 155.0.8059.39 being the affected surface; Chromium security severity is rated Medium by Google. ENISA EUVD tracks the issue as EUVD-2026-93703.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Local vector requiring an attacker-controlled co-installed app (AV:L, PR:L); no victim interaction needed (UI:N); partial confidentiality/integrity from reaching a privileged page, no availability impact.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Confused deputy in UI in Google Chrome on on Android prior to 155.0.8059.39 allowed a local attacker to bypass system access restrictions into a privileged page via a co-installed app. (Chromium security severity: Medium)
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-93703
GHSA-6h2x-8m9m-r3fc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB