EUVD-2026-50871
GHSA-g28r-c3hv-v5r3
Severity by source
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
AC:H assigned because exploitation requires a pre-compromised renderer process, making this an inherently chained, high-complexity attack; all other metrics follow the description and official vector.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in Navigation in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
UI spoofing in Google Chrome's Navigation component prior to version 151.0.7922.72 enables an attacker who has already compromised the renderer process to manipulate browser UI elements via crafted HTML pages. The Chromium team assigned Low internal severity, consistent with a CVSS score of 4.3, EPSS at the 7th percentile (0.17%), and SSVC exploitation status of 'none'. No public exploit code or active exploitation has been identified, and the vulnerability is only meaningful as a second-stage element in a multi-vulnerability attack chain.
Technical ContextAI
CWE-451 (UI Misrepresentation of Critical Information) identifies the root cause as insufficient validation of untrusted input originating from the renderer process within Chrome's Navigation subsystem. Chrome's multi-process architecture is designed so that the browser process enforces trust boundaries over renderer-supplied content; this flaw allows a compromised renderer to bypass those controls and manipulate navigation-layer UI elements such as the address bar or security indicators. The affected software is Google Chrome across all platforms prior to build 151.0.7922.72 (CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*). The Navigation component bridges the sandbox boundary between renderer and browser, making validation failures here particularly sensitive to trust-boundary confusion.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later as confirmed by the Stable Channel Update advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html). Chrome's automatic update mechanism will deliver this patch to most consumer endpoints without user action; enterprise administrators using managed policies (Google Admin Console, GPO, or MDM) should verify that update channels are not restricted and that the 151.0.7922.72 build has been pushed to all managed devices. No standalone workaround exists for the spoofing behavior itself, as it operates at the renderer-browser trust boundary; however, because exploitation first requires renderer compromise via a separate vulnerability, maintaining a fully patched Chrome installation eliminates the prerequisite attack surface and thus transitively mitigates this flaw. Additional Chromium technical details are tracked at https://issues.chromium.org/issues/514519203.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today