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 Chrome for iOS in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)
AnalysisAI
Remote code execution in Google Chrome for iOS versions prior to 149.0.7827.53 allows a remote attacker to execute arbitrary code by luring a victim to a crafted HTML page that triggers a use-after-free condition. The flaw is rated Critical by Chromium and carries a CVSS 8.8 score, and while no public exploit is identified at time of analysis, the user-interaction-only barrier (visiting a page) makes drive-by exploitation a realistic concern for unpatched iOS Chrome users.
Technical ContextAI
The vulnerability is a CWE-416 Use-After-Free memory corruption issue in Chrome for iOS, Google's Chromium-derived browser distributed through the Apple App Store. Use-after-free occurs when code continues to reference heap memory after it has been freed, allowing an attacker who controls subsequent heap allocations to place attacker-controlled data where a stale pointer is dereferenced, often yielding arbitrary code execution within the renderer process. On iOS, Chrome is constrained to use Apple's WebKit engine per App Store policy, so this bug likely resides in Chrome-specific UI, networking, or wrapper code rather than the Blink rendering engine used on other platforms.
RemediationAI
Vendor-released patch: update Chrome for iOS to version 149.0.7827.53 or later via the Apple App Store, as announced on the Chrome Releases blog at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprises managing iOS fleets via MDM should push the App Store update and verify rollout, and until devices are patched, recommend users avoid untrusted links and consider temporarily steering iOS users to Safari (which uses the same WebKit engine but is patched on its own iOS cadence) - note that this workaround does not help if the underlying defect is in Chrome-specific code unrelated to WebKit. No CVE-specific configuration flag disables the vulnerable path, so upgrading is the only durable fix.
Same weakness CWE-416 – Use After Free
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34548
GHSA-35jc-5h4r-p9cg