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
Insufficient policy enforcement in Actor in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Navigation restriction bypass in Google Chrome prior to version 149.0.7827.53 enables a remote, unauthenticated attacker to circumvent browser navigation policies by delivering a crafted HTML page to a victim. The flaw resides in the 'Actor' component of the Chromium engine, where policy enforcement is insufficient, leading to a high-integrity-impact breach (CVSS I:H) without any compromise of confidentiality or availability. No public exploit code and no active exploitation have been identified at time of analysis; EPSS stands at 0.02% (4th percentile), reinforcing a currently low real-world exploitation probability.
Technical ContextAI
The vulnerability is rooted in CWE-602 (Client-Side Enforcement of Server-Side Security), meaning that the browser's internal 'Actor' subsystem - a Blink/renderer-layer component responsible for mediating navigation policy decisions - fails to adequately enforce restrictions that should be authoritatively applied. This class of flaw arises when a client-side component acts as the gatekeeper for a policy that can be subverted through crafted inputs, bypassing controls such as cross-origin navigation guards, frame sandboxing rules, or opener/opener-policy enforcement. The affected product is Google Chrome across all platforms running versions prior to 149.0.7827.53, as identified by the EUVD entry EUVD-2026-34467 and the Chromium stable channel advisory.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later; this is the vendor-released patch confirmed by the stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's auto-update mechanism will deliver this for most users, but enterprise-managed deployments should verify policy-enforced update channels are not blocking the rollout. If immediate patching is not feasible, organizations can reduce exposure by restricting untrusted browsing on affected endpoints, deploying browser isolation solutions that proxy rendering away from the endpoint, or applying content security policies at the network perimeter to block delivery of crafted HTML from untrusted origins - noting that network-layer controls will not prevent exploitation from trusted or whitelisted domains.
Same 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-34467
GHSA-vqjx-g56x-4m94