EUVD-2026-65936
GHSA-q385-rg88-5rqr
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H reflects the mandatory renderer pre-compromise; S:C captures the sandbox-to-OS scope change; C/I/A all High reflect full arbitrary code execution outside the sandbox.
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
4DescriptionCVE.org
Improper input validation in GPU in Google Chrome on on Android prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
GPU improper input validation in Google Chrome on Android (prior to 152.0.7977.65) enables a remote attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code at the OS level via a crafted HTML page. This is a chained sandbox escape - a second-stage exploit requiring a separate renderer compromise as a prerequisite, which the AC:H CVSS rating accurately reflects. …
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 sequential conditions to be met: the attacker must first achieve code execution within Chrome's renderer process via a separate chained vulnerability, and the victim must be running Google Chrome on Android with a version prior to 152.0.7977.65. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 score (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) accurately captures this vulnerability's structure: AC:H is correct because exploitation requires a prior renderer process compromise, making this a second-stage flaw in an exploit chain. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page that first exploits a separate, chained renderer vulnerability to achieve code execution within Chrome's sandboxed renderer process on a victim's Android device. Once renderer execution is established, the attacker submits malformed GPU commands that bypass input validation in Chrome's GPU process, escaping the sandbox and achieving arbitrary code execution at OS process privilege on the Android system. … |
| Remediation | Update Google Chrome on Android to version 152.0.7977.65 or later, available via the Google Play Store automatic update mechanism or by manually navigating to Chrome Settings > About Chrome and applying available updates. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Android devices in your organization running Chrome and assess current version status. …
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 allShare
External POC / Exploit Code
Leaving vuln.today