What is the CVSS score of CVE-2026-10952?

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

Which versions of Google Chrome iOS are affected by CVE-2026-10952?

Google Chrome for iOS contains a critical code execution vulnerability affecting all users on versions older than 149.0.7827.53, creating a direct threat to the confidentiality and integrity of…. A patch is available.

How to fix or mitigate CVE-2026-10952?

Within 24 hours: Issue security alert to iOS users and device administrators regarding the vulnerability. Within 7 days: Deploy Chrome for iOS 149.0.7827.53 or later via mobile device management policies or mandatory update notifications. Within 30 days: Verify patch compliance across all iOS devices and implement policy to block outdated Chrome versions.

Google Chrome iOS CVE-2026-10952

EUVD-2026-34401 HIGH

Use After Free (CWE-416)

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

GHSA-5wxq-pmqc-mf9q

Denial Of Service Google Use After Free Memory Corruption Apple

8.8

CVSS 3.1 · Vendor: google

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

8.8 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

Analysis Generated

Jun 05, 2026 - 02:49 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 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.