Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryDeliver crafted HTML to Android Chrome
-
ExploitAbuse SignIn confused deputy
-
ExecutionBypass access restrictions to privileged page
-
ImpactDisclose restricted browser-internal data
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 victim running Google Chrome for Android on a version prior to 155.0.8059.39 to actively load attacker-controlled crafted HTML (UI:R) - e.g., by visiting a malicious or compromised web page. No authentication or prior privileges are needed (PR:N) and the attack is network-delivered (AV:N), but the mandatory user-navigation step and the Android-only, pre-patch version constraint meaningfully limit opportunistic exploitation. The specific abuse targets the SignIn component acting as a confused deputy to reach a privileged internal page; no non-default configuration is indicated as required. |
| Impact | This is a genuinely moderate-priority issue rather than a top-tier emergency, and the signals are largely consistent. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N, base 7.1) indicates a network-reachable, low-complexity, unauthenticated flaw that nonetheless requires user interaction (UI:R) - the victim must open or navigate to a crafted HTML page. That UI:R requirement is the single biggest brake on real-world risk. EPSS corroborates a low near-term exploitation likelihood at 0.22% (12th percentile), the vulnerability is NOT on the CISA KEV list, and no public proof-of-concept is referenced, so exploitation status is 'no public exploit identified at time of analysis.' Chromium itself rated the security severity only Medium, which aligns with the UI-gated, scope-unchanged (S:U) confused-deputy nature of the bug. The one notable tension is the C:H / I:L / A:N impact: the high confidentiality rating stems from bypassing access restrictions to reach a privileged internal page, but the description does not spell out exactly what data that privileged SignIn page exposes - treat C:H as vendor-assigned rather than independently verified. No SSVC decision record was provided. Overall: patch promptly given Chrome's enormous footprint, but this is a medium-severity, user-interaction-dependent issue, not evidence of active mass exploitation. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted HTML that abuses the SignIn component as a confused deputy; when an Android Chrome user (prior to 155.0.8059.39) is lured into visiting it, the page causes the browser to act with its own privileges and reach an internal privileged page the attacker should not be able to access, bypassing system access restrictions. No authentication is required but the victim must load the malicious page (UI:R). No public exploit code has been identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Remote attackers can bypass system access restrictions and reach a privileged internal page in Google Chrome for Android versions prior to 155.0.8059.39 by way of a confused-deputy weakness in the SignIn component, which performs privileged navigation on behalf of an untrusted caller. Exploitation requires the victim to load attacker-controlled crafted HTML (for example, visiting a malicious or compromised page), needs no authentication or prior privileges, and is limited to the Android build on pre-patch versions. No public exploit code has been identified at time of analysis, EPSS is low at 0.22% (12th percentile), and the issue is not confirmed as actively exploited; a vendor patch (155.0.8059.39) is available, so this is a moderate-priority patch-and-move-on item rather than an emergency.
RemediationAI
Vendor-released patch: 155.0.8059.39 - upgrade Google Chrome for Android to 155.0.8059.39 or later, delivered through Google Play (Chrome normally auto-updates; verify the installed version under Settings > About Chrome and force an update where auto-update is blocked or stale). Desktop Chrome is not indicated as affected by this specific Android SignIn issue, so remediation should be prioritized on Android fleets. Because no public exploit has been observed and EPSS is only 0.22%, standard patch-cycle prioritization is appropriate, though the unauthenticated, network-delivered nature of the attack argues for expedited rollout on high-exposure device populations. For devices that cannot be patched promptly, compensating controls are limited and imperfect: enforce a minimum Chrome version through Android Enterprise/EMM managed configurations and block installation of sideloaded or non-managed browsers (trade-off: management overhead and possible user friction); restrict browsing on sensitive devices to an allowlist of trusted destinations via managed bookmarks or a proxy/DNS filtering layer (trade-off: significant usability loss and only partial coverage of attacker-controlled content); and monitor for unexpected navigation into privileged Chrome internal pages, which is difficult to instrument in practice. None of these controls fully closes the confused-deputy path, so treat them as interim hardening until 155.0.8059.39 is deployed.
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 flaw is classified as CWE-441, Confused Deputy, a root-cause class in which a component holding legitimate privileges is tricked into exercising them for an attacker who lacks those privileges. Here the Chrome for Android SignIn flow acts as the deputy: it mediates transitions into privileged internal browser pages and, absent proper validation of the requesting origin or context, can be induced by crafted HTML to navigate into a privileged page that the web content should not be able to reach. Because the browser process itself carries the elevated capability, the access-control boundary is crossed without any memory-corruption primitive; the impact is therefore a logic/authorization bypass rather than code execution, consistent with the assessed vector showing high confidentiality impact (C:H) against low integrity impact (I:L) and no availability impact. The CPE entry cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* matches Google Chrome broadly, but both the description and the EUVD affected-version data scope this defect to the Android build before 155.0.8059.39; the referenced Chromium issue (issues.chromium.org/issues/515477538) is the upstream source of truth. It is noteworthy that Chromium's own security severity for this bug is Medium, while the derived CVSS of 7.1 reflects the confidentiality-dominant impact of reaching a privileged page and the low attack complexity (AC:L) once user navigation is achieved.
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:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
Network-delivered via a crafted page with low complexity and no auth, but victim must load the page (UI:R); impact is mainly unauthorized access to a privileged page (C:H), minor integrity, no availability.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Confused deputy in SignIn in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker to bypass system access restrictions into a privileged page via a crafted HTML page. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome for Android versions prior to 155.0.8059.39 contain a confused-deputy weakness that allows remote attackers to bypass system access restrictions and reach privileged internal pages. Organizations with mobile workforces using unpatched Android devices face potential unauthorized access to sensitive internal resources if users are tricked into visiting malicious or compromised web pages. No public exploit identified at time of analysis, and a vendor patch is available.
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
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-93718
GHSA-r6gj-589x-q7hq
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB