EUVD-2026-40612
GHSA-fc6m-85w4-chf6
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
AC:H reflects the mandatory pre-condition of a separately compromised renderer process; all other metrics align with the official vector.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Network in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Navigation restriction bypass in Google Chrome prior to 150.0.7871.47 enables a remote attacker who has already compromised the renderer process to circumvent Chrome's network navigation controls via a crafted HTML page. The vulnerability stems from CWE-20 (Improper Input Validation) in Chrome's Network component, producing a high-integrity impact with no confidentiality or availability loss. No public exploit code has been identified at time of analysis, and EPSS at 0.22% (13th percentile) places exploitation likelihood well below the median, though the pre-compromised renderer prerequisite makes this a chained attack vector relevant primarily within multi-stage browser exploitation chains.
Technical ContextAI
Google Chrome's multi-process architecture isolates web content in sandboxed renderer processes, with navigation requests mediated by the privileged browser process through strict security policies. CWE-20 (Improper Input Validation) in Chrome's Network subsystem indicates the browser process fails to adequately validate untrusted network input originating from within the renderer before processing navigation-related requests. An attacker who has already achieved renderer process control - typically via a separate JavaScript engine or media parsing vulnerability - can craft a malicious HTML page that triggers this validation gap, causing the browser process to accept navigation requests ordinarily blocked by Chrome's navigation restriction policies, such as restrictions on chrome:// privileged pages, cross-origin navigation guards, or internal resource boundaries. Per EUVD-2026-40612, affected versions are all Chrome desktop releases below 150.0.7871.47.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later; this is the vendor-released patch confirmed in the stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Updates can be applied via Chrome's built-in updater (Settings > Help > About Google Chrome) or via enterprise deployment tools (Google Admin Console, Intune, or direct MSI/PKG deployment). Because exploitation requires a prior renderer process compromise, organizations in high-risk environments should additionally enforce Chrome's strict site isolation policy (--site-per-process flag or the SitePerProcess enterprise policy), which limits renderer blast radius and raises the bar for the chained pre-condition; note that strict site isolation may increase memory usage. Filtering delivery of untrusted HTML through web proxies or secure email gateways reduces exposure to the crafted-page delivery vector but does not substitute for patching. No workaround eliminates this vulnerability without applying the patch.
Same weakness CWE-20 – Improper Input Validation
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