EUVD-2026-34475
GHSA-cx33-cm5g-9h99
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 Extensions in Google Chrome prior to 149.0.7827.53 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension. (Chromium security severity: Medium)
AnalysisAI
Navigation restriction bypass in Google Chrome's Extensions subsystem (all versions prior to 149.0.7827.53) enables circumvention of browser-enforced navigation controls when a user installs a crafted malicious extension. Rooted in CWE-284 (Improper Access Control), the flaw allows the extension to override navigation guards - potentially enabling unauthorized redirects or bypass of URL-based security policies - with a high integrity impact per CVSS (I:H). No public exploit has been identified at time of analysis, EPSS is 0.01% (1st percentile), and the vulnerability is not listed in CISA's KEV catalog, indicating low current exploitation momentum despite a medium CVSS score of 6.5.
Technical ContextAI
The vulnerability exists within Google Chrome's Extensions implementation, which exposes browser APIs (such as chrome.webNavigation, chrome.declarativeNetRequest, and chrome.tabs) allowing extensions to intercept and influence navigation events. CWE-284 (Improper Access Control) as the root cause indicates that Chrome's permission enforcement logic for extensions fails to correctly gate navigation-modifying capabilities - a crafted extension can exploit this to override restrictions that the browser is intended to enforce, such as enterprise-managed URL blocklists or same-origin navigation guards. Affected versions are all Chrome desktop releases prior to 149.0.7827.53, confirmed by ENISA EUVD-2026-34475. The Chromium issue tracker reference (https://issues.chromium.org/issues/497599683) likely contains deeper technical detail, but was not directly analyzed. No explicit CPE string was provided in the input data; the affected product is Google Chrome across all supported desktop platforms below the fixed build.
RemediationAI
The primary fix is to update Google Chrome to version 149.0.7827.53 or later, as detailed in the Google Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome auto-updates by default; administrators should verify update propagation across managed fleets via Chrome Enterprise management tooling. As a targeted compensating control for managed environments, enforce Chrome Enterprise policies restricting extension installation: use ExtensionInstallBlocklist with a wildcard (*) to block all extensions and ExtensionInstallAllowlist or ExtensionInstallForcelist to permit only IT-vetted extension IDs - this eliminates the attack prerequisite entirely, though it restricts user flexibility. Disabling sideloaded or developer-mode extensions in production endpoints also reduces exposure. Consumer users without managed policies should prioritize applying the update and avoid installing extensions from sources outside the Chrome Web Store.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today