EUVD-2026-50790
GHSA-xr6x-3wm2-3g8p
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Renderer process compromise prerequisite elevates AC to H; no target-system privileges needed; user page visit required; impact is confidentiality only.
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:H/I:N/A:N
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in Loader in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Cross-origin data leak in Google Chrome's Loader component (all versions prior to 151.0.7922.72) enables an attacker who has already compromised the renderer process to exfiltrate sensitive data from other origins via a crafted HTML page. The flaw stems from insufficient input validation (CWE-20) in how Loader processes requests originating from a compromised renderer, bypassing same-origin protections. …
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 critical, non-negotiable prerequisite for exploitation is prior compromise of Chrome's renderer process - typically achieved via a separate, unpatched RCE vulnerability in Chrome's V8 JavaScript engine, Blink renderer, or media handling stack. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor-assigned CVSS 6.5 vector (AV:N/AC:L/PR:N/UI:R) materially understates attack complexity because AC:L does not capture the most significant prerequisite: the attacker must have already compromised Chrome's renderer process, typically via a separate and often critical-severity RCE vulnerability targeting the JavaScript engine or media parser. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has separately leveraged a renderer RCE vulnerability to compromise Chrome's renderer process delivers a crafted HTML page to a victim already authenticated to sensitive internal applications. The compromised renderer exploits Loader's insufficient input validation to issue manipulated cross-origin resource requests, capturing responses - such as session tokens, CSRF nonces, or page content from banking or enterprise portals - that the same-origin policy would normally block. … |
| Remediation | Update Google Chrome to version 151.0.7922.72 or later immediately, as documented in the Chrome stable channel advisory at http://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-20 – Improper Input Validation
View allSame technique Information Disclosure
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