EUVD-2026-40710
GHSA-fgg3-fxgg-9482
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
AC raised to H because exploitation explicitly requires a prior renderer process compromise as a chained precondition, not reflected in NVD's AC:L assignment.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in Network in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Cross-origin data leakage in Google Chrome's Network component (versions prior to 150.0.7871.47) enables a remote attacker who has already achieved renderer process compromise to bypass same-origin policy protections and exfiltrate sensitive cross-origin data via a crafted HTML page. This vulnerability functions as a second-stage exploit primitive within a chain - it does not enable initial access but extends the impact of an existing renderer compromise. …
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 | Two explicit conditions must be met: first, the attacker must have already achieved code execution within the Chrome renderer process - this is a significant precondition requiring a separate, distinct vulnerability to be chained beforehand (not provided by this CVE). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD-assigned CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, score 6.5) overstates exploitability because it does not account for the explicit prerequisite stated in the description: the attacker must have ALREADY compromised the renderer process. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker crafts a malicious HTML page that first exploits a separate Chrome renderer vulnerability (e.g., a V8 engine memory corruption bug) to gain code execution within the sandboxed renderer process. With the renderer compromised, the attacker then issues specially crafted network requests that exploit the insufficient input validation in the Network component, bypassing cross-origin restrictions to read sensitive data - such as authentication tokens or private API responses - from a victim's other open browser origins. … |
| Remediation | Update Google Chrome to version 150.0.7871.47 or later via the browser's built-in update mechanism (Help > About Google Chrome) or through enterprise deployment tooling. … 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: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today