Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger UI misrepresentation in WebAppInstalls
-
ImpactSpoof trusted UI to deceive user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security UI security representation
|
| Exploitation Conditions | Requires the victim to actively load an attacker-crafted HTML page in a vulnerable Chrome build (prior to 155.0.8059.39) and interact with the WebAppInstalls UI flow (UI:R) - there is no fully passive or server-side trigger. No authentication or special privileges are needed (PR:N), and default configurations are affected, but exploitation is limited by the mandatory user interaction, the social-engineering dependency (the payoff is only deception, not code execution or data theft), and the fact that affected users are patched automatically via Chrome's update channel. |
| Impact | This is a genuinely low-priority issue despite a mid-range 5.4 CVSS. All exploitation signals point the same direction: the SSVC decision framework reports Exploitation=none, Automatable=no, and Technical Impact=partial, there is no CISA KEV listing, and no public exploit code was identified. Chromium itself rated the security severity 'Low'. The CVSS vector (AV:N/AC:L/PR:N/UI:R) shows the only real barrier is required user interaction (UI:R) - the victim must visit an attacker-controlled page. The C:L/I:N/A:L impact triple is modest, and for a CWE-451 UI-misrepresentation/spoofing bug the listed A:L (availability) and C:L (confidentiality) impacts are somewhat atypical; the practical harm is user deception rather than data loss or crash, so the recorded impact metrics likely overstate direct technical damage. No signals conflict - low EPSS-equivalent posture (no exploitation observed), no KEV, no POC, and a vendor patch already available all agree this is low real-world risk. It should be remediated via normal Chrome auto-update cadence, not treated as an emergency. |
| Exploit ScenarioDerived | An attacker hosts a crafted HTML page and lures a Chrome user (pre-155.0.8059.39) to visit it. The page abuses the WebAppInstalls flow to misrepresent or spoof UI elements, making the user believe they are interacting with a trusted interface (e.g. an install or origin prompt) to facilitate social engineering. No public exploit code is known, and exploitation requires the victim to actively visit the malicious page. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
UI misrepresentation in Google Chrome's WebAppInstalls flow - every build prior to 155.0.8059.39 - allows remote, unauthenticated attackers to spoof browser interface elements by luring a victim to a crafted HTML page and having them interact with the Web App installation prompt. The outcome is user deception rather than code execution or data theft, and exploitation is gated by mandatory user interaction (UI:R): the victim must both load the attacker's page and engage with the affected UI flow. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment rates exploitation as "none" with Automatable: no; Google rates this a Chromium security severity Low, and while the published base score of 5.4 appears mid-range, the social-engineering dependency, the deception-only payoff (integrity of what the UI communicates, not confidentiality or availability loss), and automatic delivery of the fix through Chrome's update channel keep real-world risk genuinely low.
RemediationAI
Vendor-released patch: Google Chrome 155.0.8059.39 - upgrade to that version or later (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html). Because Chrome's stable channel updates automatically, most consumer and managed devices will be remediated without user action; verify the running build at chrome://version and fully restart the browser (a lingering background process can leave an old build active), and confirm enterprise fleets have actually received the update via your management console rather than assuming silent patching succeeded. Chromium-derived browsers should be upgraded once their maintainers ship the corresponding fix. If an immediate fleet-wide upgrade is not feasible, the only meaningful compensating control is to suppress or constrain Web App/PWA installation prompts through Chrome enterprise policy for populations that do not depend on them - the trade-off being that legitimate PWA installs are blocked or degraded for those users. Standard web filtering to keep users off untrusted pages offers limited value here, since the trigger is a crafted page a user must voluntarily load and interact with, and it does not address the underlying UI misrepresentation.
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 defect lives in Chrome's WebAppInstalls component, the code path that renders installation prompts, install icons, and related chrome for Progressive Web Apps. Under CWE-451 (User Interface (UI) Misrepresentation of Critical Information), the browser fails to accurately represent security-relevant state - here, which origin or content is driving an install presentation - so attacker-controlled HTML rendered by a crafted page can be surfaced in a way that mimics trusted browser chrome or misattributes the source of an install prompt. Origin and provenance signals that users are meant to rely on for trust decisions therefore become misleading. CPE data (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) confirms a single affected product, all Chrome versions below the fixed build, across platforms, and there is no indication of a server-side or library-level component being implicated. Notably, the raw vendor feed vector scored confidentiality and availability as Low (C:L/A:L), whereas our independent assessment re-scored the vector to C:N/I:L/A:N - consistent with a pure spoofing/deception class issue that neither leaks data nor degrades availability, only the integrity of what the UI communicates.
Know when the next one hits your stack
- 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 with no privileges but required user interaction (UI:R); a CWE-451 UI-spoofing flaw harms integrity of displayed content (I:L), with no direct confidentiality or availability impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
UI misrepresentation in WebAppInstalls in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to spoof UI elements 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.
EUVD-2026-93626
GHSA-qcr3-467j-95xm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB