EUVD-2026-34361
GHSA-9688-xvff-mj4m
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
5DescriptionCVE.org
Insufficient validation of untrusted input in Extensions in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass same origin policy via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Same-origin policy bypass in Google Chrome's Extensions component prior to version 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to perform unauthorized cross-origin actions via a crafted HTML page. The vulnerability stems from insufficient input validation (CWE-20) in the Extensions subsystem and carries a CVSS integrity impact of High with no confidentiality or availability loss. No active exploitation has been confirmed - EPSS sits at 0.02% (6th percentile), SSVC exploitation status is 'none', and the CVE is not listed in CISA KEV - but a vendor-released patch is available.
Technical ContextAI
The vulnerability is rooted in CWE-20 (Improper Input Validation) within Chrome's Extensions subsystem, which processes input from the renderer process without sufficient boundary checks. The same-origin policy (SOP) is the browser's primary security primitive preventing scripts loaded from one origin from accessing resources of another; bypassing it undermines the entire web security model. Chrome's renderer process is the sandboxed component responsible for parsing and executing web content - it is intentionally isolated, but once compromised (via a separate renderer-level exploit), a second-stage bug like this one can be used to escalate impact by eroding SOP protections. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N indicates network delivery, low complexity, no privilege requirement on the attacker's side, mandatory user interaction, and that the vulnerability does not escape the current security scope.
RemediationAI
The primary fix is to upgrade Google Chrome to version 149.0.7827.53 or later, which contains the vendor-released patch as confirmed by the Chrome Releases blog at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's built-in update mechanism will deliver this automatically for most users; enterprise deployments should push the update via Google Admin Console or group policy. As a compensating control where immediate patching is not possible, restricting or disabling Chrome Extensions via enterprise policy (chrome://policy ExtensionInstallBlocklist set to '*') eliminates the vulnerable attack surface through the Extensions component, though this disables all extension functionality and may impact productivity. There is no known partial workaround that mitigates the SOP bypass while preserving extension use.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today