Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Use after free in UI in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Heap corruption in Google Chrome on Android before 149.0.7827.53 enables remote attackers to exploit a use-after-free condition in the browser's UI component through a malicious web page. The flaw carries a CVSS 8.8 (High) rating and requires user interaction (visiting a crafted page), with no public exploit identified at time of analysis. Google rates the underlying Chromium severity as High, and a vendor patch is available in the stable channel update.
Technical ContextAI
The vulnerability is rooted in CWE-416 (Use After Free), a memory-safety class where code continues to reference heap memory after it has been freed, allowing attackers to manipulate the dangling pointer to corrupt the heap. The defect resides in Chrome's UI subsystem on Android, which is built on the Chromium engine and shares much of its rendering and process-model code with desktop Chrome. Use-after-free issues in browser UI code are particularly impactful because UI components frequently run in privileged browser-process contexts, meaning successful exploitation can lead to sandbox-adjacent code execution rather than being confined to the renderer sandbox.
RemediationAI
Patch available per vendor advisory: update Google Chrome on Android to version 149.0.7827.53 or later via the Google Play Store or managed-device update channel, as documented in the Chrome Releases blog post at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html and tracked in Chromium issue https://issues.chromium.org/issues/501335606. Where immediate patching is not feasible, compensating controls include enforcing enterprise policy to block navigation to untrusted sites via URL allowlisting (trade-off: breaks legitimate browsing), deploying Site Isolation and Strict Site Isolation policies (already default but worth verifying), and instructing users to avoid clicking untrusted links until updates roll out. Disabling Chrome entirely in favor of another browser is rarely practical on Android and shifts rather than eliminates browser-engine risk.
Same weakness CWE-416 – Use After Free
View allSame technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34381
GHSA-v4qh-wp8v-x2xq