Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitOverlay or spoof Chrome UI elements
-
ExecutionVictim clicks deceptive element
-
ImpactUnintended action performed under deception
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V3 - Web Frontend Security Clickjacking prevention, X-Frame-Options
|
| Exploitation Conditions | Exploitation requires the attacker to deliver a specially crafted HTML page (via phishing, malicious link, or compromised site) AND the victim to visit and actively interact with (click) the spoofed/overlaid UI elements - this user interaction (UI:R) is the primary limiting factor. No authentication or elevated privileges are needed (PR:N), and it works against default Chrome configurations below 155.0.8059.39, but the dependence on successful social engineering substantially limits realistic impact; there is no code execution or data exfiltration, only UI deception. |
| Impact | This is a genuinely low-to-moderate priority issue despite the CVSS 5.4 'Medium' rating. The CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms remote, unauthenticated, low-complexity reach, but the mandatory user interaction (UI:R) and the clickjacking nature (CWE-1021) mean impact hinges entirely on successful social engineering rather than any direct technical compromise. No EPSS score is provided, so exploitation probability cannot be quantified; there is no CISA KEV listing and no public exploit identified at time of analysis, so there is no evidence of active or opportunistic exploitation. Conflicting signal to note: Chrome's assigned impact of C:L/I:N/A:L is atypical for a pure UI-spoofing/clickjacking flaw, where the harm is deception (an integrity concern) rather than confidentiality or availability loss - this discrepancy should be verified against the vendor's rationale. Net: a defense-in-depth browser hardening fix, not an emergency patch, though Chrome's ubiquity means it should be rolled out via normal auto-update cycles. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page that overlays or frames Chrome UI elements to deceive the victim, then lures the user to it via phishing or a malicious link. When the victim interacts with what appears to be a legitimate interface element, they are tricked into performing an unintended action. No public exploit code has been identified, and success depends entirely on the victim being socially engineered into visiting and interacting with the page. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Clickjacking in the EVP component of Google Chrome allows a remote, unauthenticated attacker to overlay and spoof UI elements by tricking a victim into visiting a crafted HTML page and clicking on concealed controls. The attack is purely a UI-redressing/deception issue - the independent assessment scores it as no confidentiality, no availability, and low integrity impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) despite the vendor's 5.4 'Medium' rating - and it succeeds only where social engineering works, with no code execution or data exfiltration. Google shipped a fix in Chrome 155.0.8059.39; no KEV listing and no public exploit code identified at time of analysis.
RemediationAI
Apply the vendor-released patch by upgrading Google Chrome to 155.0.8059.39 or later - use the built-in updater (Chrome menu > Help > About Google Chrome, or the enterprise update mechanism) and confirm the running build at chrome://version, since the fix is included in the October 2026 stable-channel update documented at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html and tracked upstream at https://issues.chromium.org/issues/517090646. No separate mitigation is published because this is a client-side UI-redressing issue, so compensating controls are necessarily risk-reduction rather than elimination: enforce automatic updates so endpoints cannot drift below 155.0.8059.39; for high-risk or executive users, disable JavaScript by default via the DefaultJavaScriptSetting enterprise policy (value 2) with allowlists for trusted sites - the trade-off is broken functionality on any site not explicitly allowlisted; block or heavily restrict browsing to untrusted/lookalike domains via enterprise URL blocklists and DNS filtering, which reduces the phishing delivery path but does not stop a compromised legitimate site; and for the highest-risk users, confine browsing to a disposable VM or remote-isolation platform so a successful click cannot reach persistent credentials, at the cost of usability and infrastructure overhead. User awareness training targeting overlay/clickjacking lures should accompany these controls but must not be treated as a technical fix. Re-check KEV and EPSS periodically: as of this analysis there is no KEV entry and no public exploit identified, so the practical priority is routine patch-cycle inclusion rather than emergency response.
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 root cause class is CWE-1021 (Improper Restriction of Rendered UI Layers or Frames), the canonical clickjacking/UI-redressing weakness in which one document can render or overlay content that visually impersonates trusted browser or page UI. Chromium normally defends against this through frame-busting checks, X-Frame-Options/CSP frame-ancestors enforcement, out-of-process iframe (OOPIF) isolation, and careful z-order/compositor handling of browser-chrome versus web-content layers; a defect in the 'EVP' component described in the Chrome stable-channel advisory means one of those layer or hit-testing restrictions could be bypassed so that a victim's click lands on an attacker-chosen element rather than the visible one. The CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms the attacker needs network reachability and no credentials or privileges, but requires the victim to interact (UI:R), which is the dominant limiting factor; the upstream Chromium issue 517090646 is the authoritative root-cause record. Exact subcomponent semantics of 'EVP' are not elaborated in the public CVE text, so the analysis is scoped to the UI-layer/framing behavior rather than a specific rendering subsystem. The associated 'XSS' tag in the source data appears to be a classification artifact of the advisory feed rather than evidence of script-injection capability, and the CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* is a vendor wildcard that does not by itself pin a version range.
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 unauthenticated page with required user click; clickjacking deceives the user (integrity I:L), with no real confidentiality or availability impact, unlike the vendor's C:L/A:L.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Clickjacking in EVP 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
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-93720
GHSA-jjmj-59p5-c94x
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB