What is the CVSS score of EUVD-2026-34364?

EUVD-2026-34364 has a CVSS 3.1 base score of 8.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Google Chrome are affected by EUVD-2026-34364?

Google Chrome for iOS contains a critical sandbox escape vulnerability (CVE-2026-10915, CVSS 8.3) that could allow attackers to compromise iOS device data if users visit malicious websites.. A patch is available.

How to fix or mitigate EUVD-2026-34364?

Within 24 hours: inventory Chrome versions across your iOS device fleet and identify affected devices. Within 7 days: deploy Chrome iOS version 149.0.7827.53 or later through your MDM platform and verify deployment compliance. Within 30 days: confirm 100% patch coverage across iOS devices, remove any devices that cannot be updated, and monitor security logs for exploitation attempts.

Google Chrome EUVD-2026-34364

| CVE-2026-10915 HIGH

Use After Free (CWE-416)

2026-06-04 chrome-cve-admin@google.com

GHSA-wg5c-5pq2-gm93

Google Memory Corruption Apple Use After Free Denial Of Service Suse Chrome Red Hat

8.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.3 HIGH

AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

SUSE

HIGH

qualitative

Red Hat

8.8 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 02:35 vuln.today

CVSS changed

Jun 05, 2026 - 02:22 NVD

8.3 (HIGH)

CVE Published

Jun 04, 2026 - 23:16 nvd

HIGH 8.3

CVE Published

Jun 04, 2026 - 23:16 nvd

UNKNOWN (no severity yet)

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