Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Link Preview in Google Chrome prior to 149.0.7827.53 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's Link Preview feature allows a remote attacker who has already compromised the renderer process to circumvent intended browsing boundaries via a crafted HTML page. All Chrome versions prior to 149.0.7827.53 on desktop are affected. The real-world threat is as a second-stage exploitation primitive within a browser attack chain - an attacker leverages this CWE-284 flaw to escape navigation controls after gaining an initial foothold in the renderer, achieving high integrity impact with no confidentiality or availability loss. No public exploit code has been identified and EPSS stands at 0.02% (4th percentile), indicating low observed exploitation probability at time of analysis.
Technical ContextAI
The vulnerability resides in Chrome's Link Preview subsystem, which generates hover or pre-navigation previews of hyperlinks. The root cause is classified as CWE-284 (Improper Access Control), indicating the Link Preview implementation fails to enforce Chrome's navigation restriction policies when operating within a compromised renderer context. In Chromium's multi-process architecture, the renderer process is intentionally sandboxed and prohibited from navigating to certain privileged or restricted origins. An 'inappropriate implementation' in how Link Preview handles crafted HTML allows these restrictions to be bypassed from within the renderer sandbox. The affected CPE is implicitly Google Chrome desktop versions prior to 149.0.7827.53 based on EUVD-reported affected version range 'Chrome 149.0.7827.53 <149.0.7827.53'. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N reflects network delivery, low complexity, user interaction required, and high integrity impact with no scope change.
RemediationAI
Vendor-released patch: Google Chrome 149.0.7827.53. Users and administrators should update all desktop Chrome installations to version 149.0.7827.53 or later using Chrome's built-in update mechanism (Settings → Help → About Google Chrome) or enterprise deployment tooling such as Google Update or Workspace device management. The stable channel update advisory is available at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Because exploitation requires a pre-compromised renderer process, organizations that cannot patch immediately should focus compensating controls on preventing initial renderer exploitation: enabling Chrome's Enhanced Safe Browsing mode to reduce exposure to malicious pages, applying Chrome enterprise policies to restrict navigation to known-safe origins via URL blocklist/allowlist, and deploying browser isolation solutions (e.g., remote browser isolation or Chromium Site Isolation hardening) to limit renderer process scope. Note that these controls address the prerequisite exploitation stage, not this specific flaw directly. No documented side effects for the patch itself.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34466
GHSA-3qq2-c4rw-569x