Skip to main content

Google Chrome EUVDEUVD-2026-93590

| CVE-2026-106338 MEDIUM
User Interface (UI) Misrepresentation of Critical Information (CWE-451)
2026-10-06 Chrome GHSA-w29j-pxvm-fmvg
5.4
CVSS 3.1 · Vendor: Chrome
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim to crafted HTML page
  2. Exploit
    Invoke Picture-in-Picture to manipulate UI
  3. Execution
    Spoof address bar to show trusted domain
  4. Impact
    Victim 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Chrome 155.0.8059.39 <155.0.8059.39

Affected Packages

euvd chrome fix: 155.0.8059.39

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

Vendor (Chrome) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
vuln.today AI 4.3 MEDIUM

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.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Red Hat 4.3 LOW

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

Lifecycle Timeline

4
CVSS changed
Oct 07, 2026 - 11:22 NVD
5.4 (MEDIUM)
Patch available
Oct 06, 2026 - 20:04 EUVD
CVE Published
Oct 06, 2026 - 18:41 cve.org
UNKNOWN (no severity yet)
CVE Published
Oct 06, 2026 - 18:41 cve.org
MEDIUM 5.4

DescriptionCVE.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

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Ubiquitous
Google Chrome is among the most widely deployed browsers worldwide
Data Quality
7 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

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

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

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

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

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

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

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

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

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

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy