Skip to main content

Google Chrome EUVDEUVD-2026-34548

| CVE-2026-10885 HIGH
Use After Free (CWE-416)
2026-06-04 chrome-cve-admin@google.com GHSA-35jc-5h4r-p9cg
8.8
CVSS 3.1 · Vendor: google
Share

Severity by source

Vendor (google) PRIMARY
8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
SUSE
HIGH
qualitative
Red Hat
9.6 HIGH
qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Analysis Generated
Jun 05, 2026 - 02:22 vuln.today
CVSS changed
Jun 05, 2026 - 02:22 NVD
8.8 (HIGH)
CVE Published
Jun 04, 2026 - 23:16 nvd
HIGH 8.8
CVE Published
Jun 04, 2026 - 23:16 nvd
UNKNOWN (no severity yet)

DescriptionCVE.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.

Vendor StatusVendor

SUSE

Severity: High
Product Status
openSUSE Tumbleweed Fixed

Share

EUVD-2026-34548 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy