EUVD-2026-65910
GHSA-27c8-3j3r-pjm4
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H reflects mandatory renderer pre-compromise prerequisite; S:C captures sandbox boundary crossing to OS context; UI:R for victim page delivery.
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 Input 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
Sandbox escape in Google Chrome for Android (versions prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside Chrome's sandbox by delivering a crafted HTML page to the victim. The vulnerability stems from improper input validation in Chrome's Input subsystem on Android, confirmed by the CVSS scope-change metric (S:C) indicating the exploit crosses the sandbox boundary. …
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 chained preconditions: (1) the attacker must have already achieved code execution within Chrome's renderer process on Android, which itself requires a separate exploitable renderer-level vulnerability; and (2) the victim must navigate to or be delivered a crafted HTML page while within that compromised renderer context (UI:R per CVSS). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) reflects theoretically severe impact tempered by high attack complexity - AC:H captures the prerequisite renderer compromise, which demands a separately exploitable renderer vulnerability before this sandbox escape can be leveraged. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer vulnerability in Chrome for Android - such as a V8 type confusion or memory corruption bug - to establish code execution within the sandboxed renderer process, then delivers a crafted HTML page that triggers the improper input validation flaw to escape the sandbox and execute arbitrary code at the Android OS privilege level. No public proof-of-concept for this specific two-stage exploit chain has been identified at time of analysis. |
| Remediation | Update Google Chrome on Android to version 152.0.7977.65 or later, as confirmed by the Chrome Stable Channel Update advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: deploy Chrome version 152.0.7977.65 or later through mobile device management (MDM) and communicate the security update to all Android users. …
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