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
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. No public exploit code has been identified and EPSS sits at 0.29% (21st percentile), consistent with this vulnerability's role as a second-stage capability in a chained browser exploit rather than a standalone attack.
Technical ContextAI
The Loader component in Chrome's browser process is responsible for fetching, routing, and dispatching web resources on behalf of renderer processes. Even after a renderer is compromised, the sandbox boundary should prevent direct cross-origin data access - but insufficient validation of renderer-supplied inputs in Loader allows a malicious renderer to manipulate resource requests or responses such that cross-origin data is returned to attacker-controlled context. CWE-20 (Improper Input Validation) identifies the root cause as a failure to adequately verify the integrity or trustworthiness of inputs arriving from the already-compromised renderer before acting on them at the browser-process level. The affected CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) covers all Chrome releases on all platforms prior to 151.0.7922.72, as confirmed by the EUVD-2026-50790 entry and the Chrome stable channel advisory.
RemediationAI
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. Chrome auto-updates by default on most consumer installations; enterprise administrators should verify deployment via Chrome Browser Cloud Management or group policy and confirm the build version is at or above 151.0.7922.72. No vendor-documented workarounds exist for this specific flaw. As a compensating control where immediate patching is blocked, consider restricting browser access to sensitive internal web applications or enforcing network-layer controls (e.g., allowlisting only trusted origins for authenticated sessions) to reduce the cross-origin data exfiltration surface - these do not remediate the flaw but raise the bar for meaningful data theft if renderer compromise occurs.
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