Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage abuses input/UI handling
-
ExecutionSpoof trusted browser UI elements
-
ImpactDeceive user into unsafe action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to actively visit an attacker-controlled crafted HTML page and be successfully deceived by social engineering (UI:R in the CVSS vector), making user interaction the primary limiting factor. No authentication or elevated privileges are needed (PR:N), and attack complexity is low (AC:L), but there is no automated or passive drive-by path - the attacker depends on luring the user and on the user trusting the spoofed interface. The flaw affects Google Chrome versions prior to 155.0.8059.39 across default configurations; updating to 155.0.8059.39 or later removes exposure. Impact is confined to UI deception within the browser rather than direct system compromise. |
| Impact | This is a genuinely medium-risk, low-priority issue despite being a Chrome vulnerability. The CVSS 3.1 base score of 5.4 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L) reflects remote, unauthenticated reach but is materially gated by UI:R - the attacker cannot act without a victim visiting a crafted HTML page and being deceived through social engineering. Chromium itself rated the security severity as Medium, consistent with the CVSS. No EPSS score, CISA KEV listing, or public POC was provided in the intelligence set, so there is no public exploit identified at time of analysis and no evidence of active exploitation - the signals are internally consistent rather than conflicting. The vulnerability class (CWE-863, Incorrect Authorization) manifesting as UI spoofing means impact is deception rather than direct code execution or data theft, further lowering real-world priority. Note: the input 'A:L' (low availability impact) is questionable for a pure UI-spoofing flaw, which is typically an integrity/deception issue rather than availability - treat the availability characterization with caution. Because Chrome is ubiquitous, patch promptly via normal browser update channels, but this does not warrant emergency out-of-band action. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page and lures a victim to visit it through social engineering (phishing link, malicious ad). When rendered, the page manipulates or spoofs Chrome UI elements so the user is misled about the browser's actual state (e.g., a trusted-looking prompt or address indication), potentially enabling follow-on credential or consent trickery. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
UI spoofing in Google Chrome versions prior to 155.0.8059.39 allows remote attackers to deceive users with fabricated browser interface elements rendered by a crafted HTML page. The flaw is an incorrect authorization check (CWE-863) in Chromium's Input component; exploitation requires the victim to open the attacker's page and be successfully socially engineered into trusting the spoofed UI (CVSS 3.1 base 5.4, AV:N/AC:L/PR:N/UI:R), with the independently assessed impact limited to integrity only (C:N/I:L/A:N). No public exploit code and no confirmed active exploitation were identified at time of analysis, and the primary limiting factor remains user interaction rather than any technical prerequisite. A vendor patch is available in Chrome 155.0.8059.39, so this is a medium-risk, low-priority hardening item rather than an urgent emergency.
RemediationAI
Update Google Chrome to version 155.0.8059.39 or later - Vendor-released patch: 155.0.8059.39 - using the built-in updater (chrome://settings/help), the enterprise MSI/PKG deployment channel, or managed auto-update policy; confirm the reported version post-upgrade since the fix also reaches users through broader stable-channel rollout. Full details are in the release advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html. Where patching cannot be immediate, compensating controls center on the user-interaction prerequisite: enforce strong phishing-resistant authentication and password managers so credentials typed into a spoofed dialog are not reusable by the attacker, block or isolate untrusted browsing destinations through DNS/web filtering or remote browser isolation (trade-off: latency, breakage of legitimate sites, and administrative overhead), and tighten enterprise policy to disable unnecessary extension and content permissions that widen the spoofable surface (trade-off: reduced functionality for line-of-business workflows). User awareness training specifically targeting in-browser UI deception reduces but does not eliminate exposure, since the attack depends on the victim trusting the fabricated interface; there is no server-side configuration that removes the flaw, so upgrading remains the only complete fix.
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 vulnerability sits in Chromium's Input component, which is responsible for routing and processing keyboard, mouse, and IME/text-entry events and for deciding which parts of the browser UI a web page is permitted to influence. CWE-863 (Incorrect Authorization) indicates that a permission or origin check governing that component was missing or incorrectly scoped, so a page could cause browser-chrome-level UI elements to be rendered or occupy states they should not. The practical consequence is interface spoofing rather than memory corruption or code execution: an attacker gains no read/write primitive, but can visually imitate trusted browser prompts or controls and thereby harvest user actions or credentials. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U confirms a network-reachable, low-complexity path with no authentication required, bounded by mandatory user interaction and a scope confined to the Chrome component, while the authoritative independent assessment assigns only an integrity impact (C:N/I:L/A:N) - consistent with deception-based abuse rather than data disclosure or denial of service. The affected CPE, cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, denotes all Chrome releases below the fixed version; the ENISA EUVD record (EUVD-2026-93728) and the Chromium issue tracker entry 517649552 both track the same defect, and Google rates it Chromium security severity Medium.
Know when Chrome 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 with no auth (AV:N/PR:N) but mandatory user deception (UI:R); UI spoofing is an integrity/deception impact (I:L), with no genuine confidentiality or availability loss.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Incorrect authorization in Input 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: Medium)
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.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
EUVD-2026-93728
GHSA-8453-c36j-7q6q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB