Skip to main content

Google Chrome CVE-2026-10951

| EUVDEUVD-2026-34400 HIGH
Use After Free (CWE-416)
2026-06-04 chrome-cve-admin@google.com GHSA-h7rf-vm92-f53j
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
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

5
Analysis Generated
Jun 05, 2026 - 20:23 vuln.today
CVSS changed
Jun 05, 2026 - 20:22 NVD
8.8 (HIGH)
CVSS changed
Jun 05, 2026 - 20: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 Autofill in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Heap corruption in Google Chrome on iOS before version 149.0.7827.53 enables remote attackers to potentially execute arbitrary code by enticing a user to interact with a malicious HTML page that triggers a use-after-free in the Autofill component. Chromium rates the underlying flaw as High severity, and while a vendor patch is available, no public exploit has been identified at time of analysis and EPSS remains very low at 0.03%.

Technical ContextAI

The vulnerability resides in Chrome's Autofill subsystem, which manages saved form data such as addresses, payment information, and credentials. CWE-416 (Use After Free) indicates that memory is referenced after it has been freed, allowing an attacker who can influence heap layout and reallocation to control the contents of the dangling pointer's target. On iOS, Chrome is required by Apple's App Store policy to use WebKit as the rendering engine rather than Blink, so the vulnerable code path lives in Chrome's iOS-specific Autofill UI/logic layer rather than the cross-platform Blink renderer. Successful exploitation typically pivots from heap corruption to arbitrary code execution within the affected browser process context.

RemediationAI

Upgrade Google Chrome on iOS to version 149.0.7827.53 or later - this is the vendor-released patch and the only complete fix. Users should update via the Apple App Store and enterprise fleets managed through MDM should push the updated build; verify deployment by checking chrome://version or the iOS App Store update history. As an interim compensating control where patching is delayed, disable Chrome Autofill (Settings → Addresses, Payment methods, and Passwords) to remove the attack surface, accepting the usability trade-off of manual form entry; alternatively, instruct users to avoid using Chrome on iOS for browsing untrusted content until the update is applied. Reference the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html for the canonical fix notice.

Vendor StatusVendor

SUSE

Severity: High
Product Status
openSUSE Tumbleweed Fixed

Share

CVE-2026-10951 vulnerability details – vuln.today

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