Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitInvoke Picture-in-Picture to manipulate UI
-
ExecutionSpoof address bar to show trusted domain
-
ImpactVictim trusts fake content and discloses credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security UI security representation
|
| Exploitation Conditions | Exploitation requires the Picture-in-Picture feature path in Chrome for Android (versions prior to 155.0.8059.39) and that the victim actively navigates to an attacker-controlled crafted HTML page (UI:R). The attack is limited to UI deception: it cannot execute code, read data, or persist, and its success further depends on the user being fooled by the spoofed address bar and then taking an action such as entering credentials. It affects Android Chrome specifically, not desktop builds, and is remediated simply by updating to 155.0.8059.39 or later. |
| Impact | This is a low-severity, low-priority issue despite a moderate 5.4 CVSS score. The provided CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L) indicates a network-reachable, low-complexity, unauthenticated flaw requiring user interaction, which aligns with the description: a victim must visit a crafted HTML page. Google/Chromium itself rated the security severity as Low, and CWE-451 (UI misrepresentation) confirms this is an address-bar spoofing/deception issue rather than code execution or data theft. No EPSS score, KEV listing, or POC was provided; there is no public exploit identified at time of analysis, so there is no evidence of active or imminent widespread exploitation. Note a signal conflict: the input CVSS impact metrics (C:L/A:L, I:N) fit awkwardly with a pure address-bar spoof, which is fundamentally an integrity-of-display/deception problem rather than a confidentiality or availability loss - this likely reflects Chrome's conservative scoring rather than genuine data disclosure or DoS. The realistic risk is phishing enablement, not direct compromise, so this ranks well below critical browser RCE or sandbox-escape bugs for patch prioritization. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page and lures an Android Chrome user to it (e.g., via a phishing link or malicious ad). Using the Picture-in-Picture feature, the page manipulates the displayed URL so the address bar shows a trusted domain while malicious content is rendered, tricking the victim into trusting or entering credentials on an attacker-controlled page. No public POC was provided, and the attack depends entirely on the user visiting the page and acting on the spoofed indicator. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Address-bar spoofing in Google Chrome for Android (versions prior to 155.0.8059.39) lets a remote, unauthenticated attacker misrepresent the browser UI through the Picture-in-Picture code path, so that a crafted HTML page can make the displayed address bar show a false origin. Exploitation requires the victim to navigate to the attacker's page and be deceived by the spoofed UI (UI:R); the flaw yields UI deception only and cannot execute code, read data, or persist. No public exploit identified at time of analysis and no CISA KEV listing; a vendor patch (155.0.8059.39) was available at release, making this a low-priority issue despite the moderate 5.4 CVSS published by NVD, which our assessment narrows to integrity impact alone.
RemediationAI
Vendor-released patch: upgrade Google Chrome for Android to 155.0.8059.39 or later through the Google Play Store, and confirm the build under Settings > About Chrome; enterprise fleets can force the minimum version via managed Google Play or Chrome Browser Cloud Management minimum-version policy. If immediate updating is not possible, the most direct compensating control is to revoke Chrome's per-app Picture-in-Picture permission in Android settings (Settings > Apps > Chrome > Picture-in-picture), which removes the vulnerable rendering path at the cost of losing PiP functionality for all sites until the update is applied; environments that cannot disable PiP system-wide can restrict it to trusted origins via policy, accepting residual exposure. Because exploitation depends on a user being fooled by a spoofed address bar, user guidance to verify origin through the full address/Security panel before entering credentials provides only marginal, unreliable protection and should not substitute for patching. Full technical detail is in the Chrome stable channel release notes (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html) and Chromium issue 448789663 (https://issues.chromium.org/issues/448789663).
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 issue is classified as CWE-451 (User Interface (UI) Misrepresentation of Critical Information) and affects the Picture-in-Picture implementation in Chrome on Android. Picture-in-Picture surfaces browser-controlled chrome - including origin/address information - alongside web content; when that rendering path mishandles a page-controlled PiP window, the trusted UI element can be presented in a context that no longer reflects the actual document origin, enabling a spoofed address bar. The CPE string cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* confirms the package is Google Chrome, with the effective affected range on Android being versions before 155.0.8059.39; desktop and other platform builds are not implicated by the Android-specific PiP path. Root-cause class is UI misrepresentation rather than memory corruption or logic bypass: no code execution, no cross-origin data read, and no persistence primitives are present. The published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L) and our independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) agree on remote, unauthenticated reach requiring user interaction, but our analysis scores only a low integrity impact on the credibility of the displayed origin.
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:L/I:N/A:L
Remote crafted page (AV:N/AC:L/PR:N) requires the victim to visit it (UI:R); impact is display integrity (I:L) for spoofing, with no confidentiality or availability loss.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
UI misrepresentation in PictureInPicture in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker to spoof address bar via a crafted HTML page. (Chromium security severity: Low)
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-93590
GHSA-w29j-pxvm-fmvg
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB