EUVD-2026-40618
GHSA-8228-r7hv-mf77
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
AC:H reflects the mandatory renderer-process compromise prerequisite stated in the description; remaining metrics align with the confirmed network delivery, required user interaction, and high confidentiality impact.
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
Inappropriate implementation in Sharing in Google Chrome on Android 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 exfiltration in Google Chrome's Sharing feature on Android exposes sensitive page content to remote attackers who have already compromised the renderer process, exploitable via a crafted HTML page. All Chrome for Android builds prior to 150.0.7871.47 are affected; the fixed release is confirmed by Google's stable channel advisory. …
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 distinct and sequential preconditions: first, the attacker must have already compromised the Chrome renderer process on the victim's Android device via a separate vulnerability - this is the primary limiting factor and a significant barrier to exploitation; second, the victim must interact with an attacker-controlled page (UI:R), meaning some degree of social engineering or malicious ad delivery is required. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD-assigned CVSS 3.1 score of 6.5 uses AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, but the AC:L assignment is materially inconsistent with the CVE description, which explicitly states renderer process compromise as a prerequisite - a condition that should elevate attack complexity to High. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker would first exploit a separate Chrome renderer vulnerability - such as a V8 type confusion or Blink memory corruption flaw - to gain code execution within Chrome's sandboxed renderer process on an Android device. With renderer access established, the attacker serves a crafted HTML page that routes sensitive cross-origin data through the Sharing subsystem's improperly controlled pathway, exfiltrating authentication tokens or private page content to attacker-controlled infrastructure. … |
| Remediation | Update Google Chrome on Android to version 150.0.7871.47 or later, which is confirmed as the vendor-released patch per the stable channel advisory at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.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-284 – Improper Access Control
View allSame technique Authentication Bypass
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