EUVD-2026-65793
GHSA-m4c2-q6hr-p6w3
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
S:C assigned because the description confirms code execution outside the renderer sandbox, which crosses a defined security boundary - the official S:U designation appears to be an error.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Buffer overflow in ANGLE in Google Chrome on on Android prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Heap-based buffer overflow in ANGLE (Almost Native Graphics Layer Engine) within Google Chrome for Android prior to 152.0.7977.65 enables remote code execution outside the renderer sandbox via a crafted HTML page, meaning a successful attacker escapes Chrome's process isolation boundary with full C/I/A impact. Exploitation requires no authentication and only that a victim navigate to an attacker-controlled page, making drive-by compromise via phishing or malvertising a realistic delivery path. …
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 | The target must be running Google Chrome for Android in any version prior to 152.0.7977.65. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The official CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) contains a notable internal inconsistency: the S:U (scope unchanged) designation conflicts with the CVE description's explicit statement that code executes 'outside the sandbox,' which is definitionally a scope change under CVSS 3.1 semantics and should be scored S:C - this discrepancy is unresolved in the available references and should be verified with Google's security team. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers or compromises a website and embeds a crafted HTML page containing malformed WebGL operations designed to trigger a heap overflow in Chrome's ANGLE graphics layer. A victim on an unpatched Android device visits the page via a phishing link or malicious advertisement, the overflow is triggered in the renderer process, and the attacker achieves code execution outside the Chrome sandbox - gaining access to the device at Chrome's process privilege level, enabling credential theft, surveillance, or further lateral movement. … |
| Remediation | Update Google Chrome for Android to version 152.0.7977.65 or later immediately via the Google Play Store; this is the vendor-released patch 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, audit all mobile device inventory through MDM and asset management systems to identify Chrome for Android instances, and immediately notify affected users to update to version 152.0.7977.65 or later as a critical security patch. …
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 allShare
External POC / Exploit Code
Leaving vuln.today