Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage manipulates browser UI rendering
-
ExecutionSpoofed UI elements appear legitimate
-
ImpactVictim trusts fake interface and is deceived
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 victim to visit an attacker-crafted HTML page in Chrome versions prior to 155.0.8059.39 AND to be successfully deceived through social engineering into trusting the spoofed UI elements. The limiting factors are significant: mandatory user interaction (UI:R) means the attack cannot succeed passively or at scale, and it relies on convincing social engineering rather than any technical bypass. The flaw affects default Chrome configurations (no special feature or non-default setting is named in the description), but impact is confined to UI deception on the affected desktop browser build; patched versions are not vulnerable. |
| Impact | This is a low-severity UI spoofing flaw (CWE-451) that the signals consistently rank as a low real-world priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U, base 5.4) indicates a network-reachable, unauthenticated, low-complexity issue, but crucially requires user interaction (UI:R) - the victim must be lured to and act on a crafted HTML page. Google/Chromium itself rated the security severity 'Low'. The SSVC decision framework reinforces this: Exploitation=none (no observed or public exploitation), Automatable=no (requires per-victim social engineering, cannot be mass-scripted), Technical Impact=partial. There is no CISA KEV listing and no public POC reported, so exploitation status is 'no public exploit identified at time of analysis.' EPSS was not provided in the input, so exploitation probability cannot be quantified here. One inconsistency to flag: the input CVSS impact metrics (C:L/I:N/A:L) do not align well with a pure UI-misrepresentation/spoofing weakness, which is fundamentally an integrity-of-display issue rather than a confidentiality or availability one - verify impact mapping with the vendor advisory. Net assessment: genuinely low priority despite the ubiquity of Chrome, because the defect enables deception rather than code execution or data theft and depends entirely on successful social engineering. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page and, using social engineering (e.g., a phishing link), lures a Chrome user to visit it. The page manipulates browser UI elements so that spoofed content (such as a forged address bar, dialog, or security indicator) appears legitimate, tricking the victim into trusting fraudulent information or taking an unsafe action. No public exploit code is identified at time of analysis, and the attack requires the user to visit and interact with the attacker-controlled page. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
UI spoofing in Google Chrome desktop builds prior to 155.0.8059.39 allows a remote attacker to misrepresent browser UI elements to a victim through a crafted HTML page, potentially deceiving the user into trusting content that does not correspond to the real page or origin. Exploitation is not passive: it requires the victim to visit the attacker-controlled page and then be successfully manipulated via social engineering, which is why the independent assessment scores the vector as AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N - a low-integrity-only impact with no confidentiality or availability loss. No public exploit code or active exploitation has been identified at time of analysis, CISA's SSVC framework rates exploitation as none and automatable as no with only partial technical impact, and vendor-released patches are available in Chrome 155.0.8059.39.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 155.0.8059.39 or later. On managed fleets, push the 155.0.8059.39 stable build through your enterprise update mechanism (Chrome auto-update, or an MSI/PKG deployment) and verify the running build via chrome://version, ensuring the browser is fully restarted so the new binary is actually in use; unmanaged users should check chrome://settings/help and relaunch. There is no configuration flag, policy toggle, or feature switch that disables the affected UI rendering path, so patching is the only complete fix, and disabling JavaScript, blocking third-party content, or tightening site-isolation settings would not reliably prevent a UI-spoofing page from being rendered. Compensating controls while patching is pending carry trade-offs and are only partial: enforcing an enterprise URL blocklist or Safe Browsing-enhanced protections may reduce exposure to known malicious pages but cannot catch a bespoke crafted HTML page; user-awareness training against social-engineering prompts reduces the UI:R requirement's success rate but does not remove the vulnerability; and restricting browsing to trusted origins is operationally heavy and breaks normal workflows. Because the CVSS vector requires PR:N with UI:R, and given that no public exploit code or active exploitation has been identified at time of analysis, patching on the normal low-severity maintenance cadence is appropriate, with priority given to users who routinely handle credential or payment prompts in the browser.
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-451 (User Interface (UI) Misrepresentation of Critical Information) and lives in Chrome's UI layer rather than in a memory-safety or script-execution component, meaning the attacker does not gain code execution or read protected data - the harm is that the browser chrome (address/origin indicators, prompts, dialogs, or similar trust-bearing elements) can be rendered in a way that misleads the user about what they are interacting with. The attack surface is the Chromium HTML/CSS rendering and UI compositing pipeline reached by a crafted HTML page; the CVSS vector confirms network reachability (AV:N), no privileges required (PR:N), but mandatory user interaction (UI:R), so the attacker must both deliver the page and convince the target through social engineering. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* with the EUVD version range indicating Chrome builds before 155.0.8059.39 covers default desktop Chrome configurations; no non-default feature or setting is named as a precondition, and there is no indication that Chrome's process sandbox, site isolation, or memory protections are relevant to this class of bug. The Chromium security severity is explicitly Low, consistent with the SSVC assessment of partial technical impact and no exploitation, and consistent with the authoritative independent vector that assigns integrity-only impact.
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 needs no privileges but mandatory user interaction (UI:R); UI spoofing is a display-integrity issue (I:L) with no genuine confidentiality or availability loss.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
UI misrepresentation in UI in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering 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-93625
GHSA-246m-48p5-p669
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB