Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered via crafted page (AV:N, UI:R); AC:H because a prior renderer compromise is required; PR:N as no auth needed; S:C and C/I/A:H reflect sandbox escape to GPU process.
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
Heap buffer overflow in GPU in Google Chrome on Android prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
AnalysisAI
Sandbox escape in Google Chrome on Android prior to 149.0.7827.115 allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a crafted HTML page that triggers a heap buffer overflow in the GPU process. Chromium rates this severity Critical, and while no public exploit identified at time of analysis, the bug is part of a classic two-stage exploitation chain typically used in browser zero-day exploits. …
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 (1) Chrome for Android at a version below 149.0.7827.115, (2) the attacker already holding code execution inside the renderer process - typically achieved via a chained renderer bug, since the GPU heap overflow is not reachable from ordinary JavaScript or unprivileged web content alone, and (3) user interaction to load a crafted HTML page in the vulnerable Chrome instance. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H yields 8.3 (High), driven by the scope change (sandbox escape) and full CIA impact, tempered by High attack complexity (requires a prior renderer compromise) and required user interaction (visiting a crafted page). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A targeted user on Android with an unpatched Chrome is lured to a malicious page that first exploits an unrelated renderer bug to gain code execution inside the sandboxed renderer, then sends crafted GPU commands that trigger the heap overflow in the GPU process to escape the sandbox and run code with GPU-process privileges. From there the attacker can pivot further into the Android OS via GPU-driver bugs, enabling spyware-style implant deployment. … |
| Remediation | Vendor-released patch: Chrome 149.0.7827.115 - update Chrome for Android to 149.0.7827.115 or later via Google Play, which is the only durable fix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Android devices running Chrome and assess current version distribution against Chrome 149.0.7827.115. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36331
GHSA-7mrw-37c7-gw8p