EUVD-2026-50826
GHSA-9vrw-vg3x-9vqg
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Renderer process compromise is an explicit prerequisite, raising real-world attack complexity to High; impact limited to partial cross-origin confidentiality disclosure 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:L/I:N/A:N
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in Actor 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 leakage in Google Chrome's Actor component (all versions prior to 151.0.7922.72) allows a remote attacker who has already compromised the renderer process to exfiltrate sensitive cross-origin data via a crafted HTML page. This is a secondary-stage information disclosure primitive - it requires both user interaction and a pre-compromised renderer, making it a chained exploit component rather than a standalone entry point. …
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 two explicit preconditions: (1) the victim must visit or be redirected to a crafted HTML page (user interaction required, per UI:R in the CVSS vector), and (2) the attacker must have already compromised the Chrome renderer process through a separate, independent vulnerability - this prerequisite is explicitly stated in the CVE description and is the primary limiting factor on real-world exploitability. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The official CVSS 3.1 score of 4.3 (Medium) correctly reflects limited impact: C:L (partial confidentiality breach), I:N, A:N, with UI:R requiring user interaction. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already achieved renderer process compromise in Chrome - through a separate, chained renderer vulnerability - directs the victim to a specially crafted HTML page. The page triggers the flawed Actor component with malicious untrusted input that bypasses cross-origin validation, leaking sensitive data (such as authentication tokens or page content from another origin loaded in the browser) back to the attacker-controlled renderer context. … |
| Remediation | Update Google Chrome to version 151.0.7922.72 or later, as confirmed by 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-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