Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Core in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome on iOS prior to 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. The flaw is a use-after-free in the Core component rated High severity by Chromium, and no public exploit identified at time of analysis. Exploitation requires user interaction (visiting a malicious page) and chaining with a prior renderer compromise, raising the practical bar despite the 8.3 CVSS score.
Technical ContextAI
The issue is a CWE-416 Use-After-Free in Chrome's Core component on the iOS platform. Use-after-free occurs when memory is referenced after being freed, allowing an attacker who controls heap layout to substitute attacker-controlled data into the freed object and hijack control flow or corrupt state. In Chromium's multi-process architecture, the renderer process is sandboxed and a separate browser/Core process mediates privileged operations; a UAF reachable from the renderer-to-browser boundary can be leveraged to escape the sandbox. On iOS specifically, Chrome uses Apple's WebKit under the hood for rendering, but Chrome-specific Core code still mediates IPC and platform integration, which is where this flaw resides.
RemediationAI
Vendor-released patch: Chrome for iOS 149.0.7827.53 or later - update via the Apple App Store immediately, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html). For managed fleets, push the updated app through MDM (Intune, Jamf, Workspace ONE) and enforce minimum-version policies for Chrome on iOS. As a compensating control until patching, instruct users to use Safari or another up-to-date browser for untrusted browsing, or restrict Chrome on iOS to known-trusted sites via MDM web content filtering; the trade-off is user friction and partial loss of Chrome-specific sync/profile features. Because this bug requires a renderer compromise to reach, keeping the underlying iOS and WebKit stack patched also reduces realistic exploitability.
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-34364
GHSA-wg5c-5pq2-gm93