EUVD-2026-50789
GHSA-hj3x-vvv3-2vj4
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H and UI:R capture the required prior renderer compromise plus victim loading crafted content; S:C reflects the GPU-process escape, with total C/I/A impact per Chromium's assessment.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in GPU in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome for Android before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the browser sandbox through crafted input to the GPU component. This is a second-stage vulnerability (CWE-20, improper input validation) that Google rates High severity and CVSS 8.3 with a scope change; it is chained after an initial renderer bug rather than exploited alone. …
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 the attacker to have already compromised the renderer process on an Android device running Google Chrome before 151.0.7922.72, and then deliver a crafted HTML page whose input targets the GPU component to escape the sandbox. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and point to a genuine-but-conditional priority rather than a mass-exploitation emergency. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first lands a separate renderer-process exploit (for example via a malicious ad or compromised site the victim visits), then serves a crafted HTML page whose payload sends malformed input from the controlled renderer to the GPU process, escaping the sandbox to run with GPU-process privileges. The attack requires the victim to load attacker content (UI:R) and is non-trivial to chain (AC:H). … |
| Remediation | Vendor-released patch: 151.0.7922.72 - update Google Chrome for Android to 151.0.7922.72 or later via the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html); on Android this typically arrives through Google Play, so ensure automatic app updates are enabled and force-update managed fleets via MDM. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, notify infrastructure and security teams and verify inventory of all Android devices running Chrome to establish baseline deployment scope. …
Sign in for detailed remediation steps and compensating controls.
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