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 potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Heap corruption in Google Chrome for iOS prior to 149.0.7827.53 allows remote attackers to potentially execute arbitrary code by luring a user to a crafted HTML page that triggers a use-after-free condition. Google has rated this as High severity and a vendor patch is available, though no public exploit has been identified at time of analysis. The CVSS 8.8 score reflects network-reachable exploitation with low complexity but requires user interaction (visiting a malicious page).
Technical ContextAI
The vulnerability is a CWE-416 Use-After-Free flaw in Chrome for iOS, Google's mobile browser built on a WebKit-based engine (as required by Apple's iOS App Store policies for browsers) layered with Chromium's higher-level browser logic. Use-after-free bugs occur when memory is freed but a dangling pointer is subsequently dereferenced, allowing an attacker who can influence heap allocation patterns to place attacker-controlled data into the freed region and corrupt object state. In a browser context, such flaws are typically triggered by JavaScript or DOM manipulation embedded in an HTML page, and successful exploitation can pivot from heap corruption to control-flow hijack, enabling code execution within the renderer process sandbox.
RemediationAI
Apply the vendor-released patch by upgrading Google Chrome for iOS to version 149.0.7827.53 or later via the Apple App Store; this is the primary and authoritative fix as confirmed by Google's Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprises managing iOS fleets via MDM should push the updated Chrome build and verify installed versions across devices. As a compensating control while updates roll out, instruct users to avoid following untrusted links and consider temporarily using Safari (which is also WebKit-based but unaffected by Chromium-layer flaws) or disabling Chrome on iOS; note the trade-off is loss of Chrome sync and extension/profile continuity. Network-level URL filtering or Safe Browsing enforcement can reduce exposure to known malicious pages but will not block targeted or novel attacker infrastructure.
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-34401
GHSA-5wxq-pmqc-mf9q