Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Requires a pre-compromised renderer foothold (PR:L) plus chained conditions (AC:H) and victim loading content (UI:R); yields high confidentiality/integrity loss with no availability impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Passwords in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
AnalysisAI
Site isolation bypass in Google Chrome prior to 151.0.7922.72 lets a remote attacker who has already compromised the renderer process read or tamper with data belonging to other origins by serving a crafted HTML page, defeating one of Chrome's core sandbox boundaries. Chromium rates the severity High and a fixed Stable-channel build has shipped; there is no public exploit identified at time of analysis and EPSS is low at 0.30% (23rd percentile). …
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 | Exploitation requires that the attacker has ALREADY compromised the Chrome renderer process - this is an explicit prerequisite in the CVE description, not a network-facing entry point - and then delivers a crafted HTML page to bypass Site Isolation; the CVSS UI:R metric means the victim must load attacker-controlled content. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are mixed and point to a genuine-but-conditional risk. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate memory-corruption bug to gain control of a Chrome renderer process, then uses that foothold to serve a crafted HTML page that abuses the Passwords input-validation flaw to slip past Site Isolation and read cross-origin data such as saved passwords or other sites' content. Given UI:R, the victim must load attacker-influenced content, and no public exploit is currently identified, so this would be part of a bespoke exploit chain rather than commodity malware. |
| Remediation | Vendor-released patch: Google Chrome 151.0.7922.72; upgrade all Desktop Chrome installations to 151.0.7922.72 or later and restart the browser to apply, verifying via chrome://settings/help and the Stable Channel 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. |
Recommended ActionAI
Within 24 hours: Deploy Chrome version 151.0.7922.72 or later to all endpoints through your organization's patch management system and verify auto-update is enabled. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
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
EUVD-2026-50812
GHSA-v45v-wj9p-hx85