EUVD-2026-50631
GHSA-g3c9-mhvm-x87q
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Site isolation bypass crosses origin process boundaries implying S:C; extension install requires active user action (UI:R, PR:N); C:L added since cross-origin access likely exposes some data.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Lifecycle Timeline
5DescriptionCVE.org
Policy bypass in Extensions in Google Chrome prior to 151.0.7922.72 allowed an attacker who convinced a user to install a malicious extension to bypass site isolation via a crafted Chrome Extension. (Chromium security severity: Medium)
AnalysisAI
Policy bypass in the Extensions subsystem of Google Chrome (all versions prior to 151.0.7922.72) allows site isolation circumvention when a user is convinced to install a crafted malicious extension. The CVSS vector (I:H, S:U) and CWE-693 indicate this is a protection mechanism failure that undermines Chrome's cross-origin boundary enforcement, potentially enabling manipulation of content across isolated sites. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The singular and non-negotiable prerequisite is that the victim user must install the attacker-controlled Chrome extension - this is the UI:R condition in the CVSS vector and the central attack dependency. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 6.5 Medium score is driven by AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N, reflecting network-deliverable, low-complexity exploitation with no attacker privileges required but mandatory user interaction (installing the malicious extension). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker develops a Chrome extension that appears legitimate - a productivity tool, ad blocker, or theme - and distributes it via phishing email, a deceptive website, or by submitting it to the Chrome Web Store under a benign guise. Once a victim installs the extension, it invokes the policy bypass to cross Chrome's site isolation boundary, allowing the extension to manipulate or read content from origins (e.g., banking or corporate intranet sites) that the extension should have no access to. … |
| Remediation | The primary fix is to update Google Chrome to version 151.0.7922.72 or later, available through Chrome's built-in auto-update mechanism or directly via the vendor advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-693 – Protection Mechanism Failure
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today