EUVD-2026-61232
GHSA-cqjc-f8j4-5vqq
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; S:C captures sandbox escape; PR:N because attacker serves the exploit page without needing an account.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Buffer overflow in ANGLE in Google Chrome on on Android prior to 151.0.7922.169 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape via heap-based buffer overflow in ANGLE's graphics engine on Chrome for Android allows a threat actor who has already achieved renderer process compromise to execute arbitrary code entirely outside the Chrome sandbox. All Chrome for Android versions prior to 151.0.7922.169 are affected; the vulnerability requires a two-stage exploit chain combining a separate renderer compromise with this ANGLE flaw. …
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 | Two distinct prerequisites must both be satisfied: (1) the attacker must have already compromised the Chrome renderer process via a separate, unrelated vulnerability - this is an explicit prerequisite stated in the CVE description, not an inferred condition; (2) a user must navigate to or be redirected to a crafted HTML page that triggers the malicious graphics operations (UI:R from CVSS). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 base score reflects the full C:H/I:H/A:H impact triad and a scope change (S:C), which captures the sandbox-escape characteristic accurately. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker operates a two-stage attack: first exploiting a separate renderer-level vulnerability (e.g., a JavaScript engine or DOM parser bug) to gain code execution within Chrome's sandboxed renderer process on an Android device. The attacker then serves the victim a crafted HTML page containing WebGL or graphics API calls designed to trigger the ANGLE heap buffer overflow, corrupting renderer heap memory in a controlled way to pivot code execution outside the sandbox and into the broader Android process space. … |
| Remediation | The primary remediation is updating Google Chrome for Android to version 151.0.7922.169 or later, as documented in the vendor's stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0826575033.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, conduct an inventory of Chrome for Android deployments across your mobile device estate, flagging any devices accessing sensitive systems or data repositories. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-122 – Heap-based Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today