Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious co-installed Android app
-
ExploitTrigger Chrome information-leak condition locally
-
ImpactExfiltrate sensitive browser data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a separate attacker-controlled app to already be co-installed on the same Android device as Chrome (versions prior to 155.0.8059.39); it cannot be triggered remotely over the network. The CVSS AC:H rating indicates additional non-deterministic conditions (such as timing or specific device/app state) must be met, further limiting reliability. No user interaction or authentication is required once the malicious app is present, but the need to first place a hostile app on the device is the primary limiting factor. Desktop and non-Android Chrome builds are not in scope per the description. |
| Impact | This is a moderate-severity, low-real-world-priority issue. The provided CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, base 5.1) is internally consistent with the description: the attack vector is explicitly local (AV:L) because exploitation requires a co-installed malicious app already present on the same Android device, and attack complexity is High (AC:H), implying the attacker must win a race or satisfy conditions outside their control. Although privileges are None (PR:N) and no user interaction is needed, the local-only vector and high complexity sharply constrain real-world exploitability - an attacker must first get a hostile app onto the victim's device. No EPSS score was supplied, the CVE is not in CISA KEV, and no public proof-of-concept is referenced, so there is no public exploit identified at time of analysis. The confidentiality-only impact (C:H, I:N, A:N) means successful exploitation leaks sensitive information but does not grant code execution or integrity/availability loss. Net: a legitimate but low-urgency patch-cycle item rather than an emergency, driven by the local vector, high complexity, and absence of any exploitation signal. |
| Exploit ScenarioDerived | A user installs a malicious or compromised app from the Play Store or a sideloaded source onto an Android device that also runs Chrome. The hostile app leverages the co-installed-app information leak to read sensitive data belonging to Chrome without any user interaction or elevated privileges, though it must satisfy the high-complexity timing/condition requirements. No public exploit is currently known. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Local information disclosure in Google Chrome on Android versions prior to 155.0.8059.39 allows a co-installed malicious app to access sensitive information without user interaction or authentication, though exploitation requires high attack complexity and the pre-existence of an attacker-controlled app on the same device. This moderate-severity issue (CVSS 5.1) has no public exploit identified at time of analysis, and vendor patch 155.0.8059.39 is available.
RemediationAI
Vendor-released patch: upgrade Google Chrome on Android to version 155.0.8059.39 or later via the Google Play Store. No workarounds are necessary beyond updating; however, users can reduce risk by uninstalling unnecessary or untrusted apps, as the attack requires a co-installed malicious app. The Chrome release blog (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html) and Chromium issue 557036053 (https://issues.chromium.org/issues/557036053) provide further details. No public exploit code or active exploitation has been identified at time of analysis.
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 vulnerability is classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and affects Google Chrome on Android, as identified by the CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* (platform-specific: Android). The CVSS vector CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N indicates a local attack vector (AV:L), high attack complexity (AC:H) due to non-deterministic conditions such as timing or specific device states, no privileges required (PR:N), no user interaction (UI:N), and high confidentiality impact (C:H) with no integrity or availability impact. The root cause likely involves insufficient access controls in Chrome's Android inter-process communication or data storage, allowing a co-installed app to read sensitive data. Desktop and non-Android Chrome builds are not affected. Exploitation is constrained by the need for a separate attacker-controlled app to already be present on the device, making real-world exploitation low priority.
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:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Local co-installed app yields AV:L, non-deterministic conditions give AC:H, no privileges or interaction needed (PR:N/UI:N), and the flaw only leaks data so C:H with I:N/A:N.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Information leak in Mobile in Google Chrome on on Android prior to 155.0.8059.39 allowed a local attacker to obtain sensitive information 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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-93584
GHSA-2gx3-fw76-jcfq
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB