Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSocially engineer victim to crafted page
-
ExploitVictim opens page in vulnerable Chrome
-
ExecutionTrigger info leak in Passwords component
-
ImpactExfiltrate disclosed sensitive 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 | Requires the victim to be running Google Chrome on Android at a version prior to 155.0.8059.39, and to be socially engineered into opening an attacker-crafted HTML page (UI:R) - the leak cannot be triggered without this user interaction. No authentication or elevated privileges are needed (PR:N) and no non-default configuration is indicated, so default Android Chrome installs are affected. The user-interaction/social-engineering requirement and the vendor's 'Low' severity rating are the key limiting factors; disclosure is confined to sensitive information handled by the Passwords component rather than full device or account compromise. |
| Impact | Signals conflict sharply. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H = 8.8) rates this as High with full confidentiality, integrity AND availability impact, yet the vulnerability is a CWE-200 information leak in Chrome's Passwords component that Google's own Chromium security team rated 'Low'. An information-disclosure flaw should not carry I:H/A:H - the supplied vector appears inflated and inconsistent with both the description and the vendor's own severity, so the 8.8 should NOT be treated as the operative priority. There is no CISA KEV listing and no public exploit identified at time of analysis, and no EPSS score was provided, so there is no evidence of active or imminent exploitation. Exploitation also requires user interaction (UI:R) driven by social engineering, which further reduces real-world risk. Net assessment: despite the headline 8.8, this is a low-to-moderate real-world priority - a vendor-rated Low info leak with a patch already available; apply the Chrome update in normal patch cycles rather than as an emergency. |
| Exploit ScenarioDerived | An attacker socially engineers an Android Chrome user into visiting a crafted HTML page; when the victim opens it in a vulnerable Chrome build, the page triggers the Passwords-component information leak and discloses sensitive data to the attacker. No authentication is required (PR:N) but the attack cannot succeed without the victim's interaction (UI:R). No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Information disclosure in Google Chrome for Android lets a remote attacker who successfully socially engineers a victim into opening a crafted HTML page expose sensitive data handled by the browser's Passwords component; builds prior to 155.0.8059.39 are affected, and no authentication or non-default configuration is required. The vendor classifies the issue as Low severity (CWE-200) and no public exploit code was identified at time of analysis. Note that the supplied CVSS base score of 8.8 (C:H/I:H/A:H) is inconsistent with the information-disclosure description and the vendor's Low rating; our independent assessment scores it AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, i.e. a confidentiality leak that strictly depends on user interaction.
RemediationAI
Vendor-released patch: 155.0.8059.39 - Google has shipped a fix in the Chrome stable channel, so the primary action is to update Chrome on Android to 155.0.8059.39 or later via Google Play (or the vendor's managed deployment path), and to confirm the installed version in Chrome's Settings > About Chrome screen; refer to the release note at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html and the tracking issue at https://issues.chromium.org/issues/553335319. Until managed fleets are fully updated, compensating controls should target the social-engineering trigger and the Passwords component itself: restrict or disable saved-password storage and autofill in Chrome on Android (Android Settings > Google > Autofill/Password Manager, or chrome://settings/passwords where reachable), and require employees to use a separate, vetted password manager instead - the trade-off is reduced convenience and extra helpdesk load, and users who keep credentials in a third-party manager must ensure it is not exposed through Chrome's autofill integration. Blocking or warning on untrusted links and enforcing safe-browsing/URL-blocklist policies at the network or MDM layer reduces the likelihood of the UI:R prerequisite being satisfied, at the cost of possible false positives on legitimate sites. Because exploitation requires the victim to open a crafted page, awareness messaging about unsolicited links is a reasonable stopgap, but it is not a substitute for patching. No vendor workaround that preserves the Passwords functionality completely was identified in the source data.
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
CVE-2026-106256 is rooted in CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and lives in the Passwords component of Chrome on Android - the browser's credential store/autofill subsystem that holds saved logins. The attack path is client-side and non-memory-corruption: a crafted HTML page, once rendered after the victim is lured to it (CVSS UI:R), causes the browser to disclose information from that password-handling component instead of keeping it isolated per-origin. There is no indication of code execution, memory corruption, privilege escalation, or state modification, which is why the integrity and availability metrics of the supplied 8.8 score are not supportable; the observed impact is confidentiality-only and limited (C:L) per our independent assessment. The CPE record cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* is a broad wildcard covering the Chrome product line, while the description and ENISA EUVD entry (EUVD-2026-93637) narrow the exposure to Chrome on Android before the fixed build. Chromium's own security severity rating is Low, and the referenced tracker is https://issues.chromium.org/issues/553335319.
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
Sources disagree (Low–High)AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page needing victim interaction (AV:N/UI:R, PR:N); as a CWE-200 info leak rated Low by the vendor, confidentiality is limited (C:L) with no integrity or availability impact.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Information leak in Passwords in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: Low)
Executive ViewAI
Google Chrome for Android builds below 155.0.8059.39 carry an information-disclosure weakness in the browser's password component that could expose stored credentials if an employee is socially engineered into opening a crafted web page on a mobile device. The exposure requires no authentication on the attacker's side and no special configuration, but it does depend on a user clicking into attacker-controlled content, so risk is concentrated on the human element rather than automated mass compromise, and no public exploit identified at time of analysis. Leadership should care because affected devices are typically personal or BYOD phones holding both corporate credentials and the user's personal passwords, and a vendor patch is already available, making this a patch-compliance and user-awareness issue rather than a zero-day response.
Apply vendor patch.
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-93637
GHSA-7hvw-ccrx-5cx9
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB