EUVD-2026-40617
GHSA-73h2-64hc-q23c
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
AC:H reflects the explicit prerequisite that the renderer process must already be compromised before this UI spoofing can occur, raising real-world attack complexity above the provided vector.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Media in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
UI spoofing in Google Chrome on Windows (prior to 150.0.7871.47) allows a remote attacker who has already compromised the renderer process to manipulate the browser interface via a specially crafted HTML page, potentially deceiving users into interacting with falsified content or controls. The vulnerability stems from an inappropriate implementation in the Media component and is classified as medium severity (CVSS 6.5). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires two sequential conditions: first, the attacker must have already successfully compromised the Chrome renderer process on the target Windows system via a separate, unrelated vulnerability - this is a non-default, non-trivial precondition that implies chaining exploits. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 6.5 score with vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N reflects a network-reachable, high-integrity-impact flaw, but this vector warrants scrutiny: PR:N and AC:L appear optimistic given that the CVE description explicitly requires the attacker to have already compromised the renderer process - a significant non-trivial precondition that implies chaining with a separate renderer exploitation. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already exploited a separate Chrome renderer vulnerability on a Windows host delivers a crafted HTML page that abuses the media component's inappropriate implementation to manipulate the browser's trusted UI chrome - for example, spoofing the address bar, dialog boxes, or permission prompts - causing the victim to believe they are interacting with a legitimate, trusted origin when they are not. No public proof-of-concept code has been identified, and this attack requires chaining with a renderer exploit, making opportunistic mass exploitation unlikely at this time. |
| Remediation | Update Google Chrome on Windows to version 150.0.7871.47 or later, which is confirmed to include the fix per the vendor advisory at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today