# CVE-2026-10951: Google Chrome for iOS use after free in Autofill

Source: https://junglewise.ai/threats/cve-2026-10951-google-chrome-for-ios-use-after-free-in-autofill  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-04. Updated: 2026-06-04  
License: CC BY 4.0 with a link back

CVE-2026-10951 · Severity: info · CVSS 8.8 · Published 2026-06-04

A security vulnerability exists in the Autofill feature of Google Chrome for iOS. An attacker could trick a user into performing specific touch gestures on a malicious website to trigger a memory error. This could allow the attacker to potentially crash the browser or execute unauthorized code on the device.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-10951 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-10951 being exploited in the wild.

**How severe is CVE-2026-10951?** Informational severity, with a CVSS score of 8.8, published 4 June 2026.

**Which products and versions are affected?** Google Chrome prior to 149.0.7827.53.

**Is there a fix for CVE-2026-10951?** A patch was published on 2026-06-02: Chrome 149.0.7827.53 released to stable channel. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-10951 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-10951?** Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A use-after-free (UAF) vulnerability exists in the Autofill component of Google Chrome for iOS prior to version 149.0.7827.53. The flaw is triggered when a user is convinced to perform specific UI gestures on a malicious HTML page, leading to heap corruption. This vulnerability class (CWE-416) typically occurs when the application continues to use a pointer after the memory it points to has been freed, which can be leveraged by a remote attacker for arbitrary code execution or a denial-of-service (DoS) attack. Google has addressed this issue in the stable channel update 149.0.7827.53.

## Affected products

- Google Chrome for iOS prior to 149.0.7827.53

## Timeline

- 2026-06-02: patched: Chrome 149.0.7827.53 released to stable channel.
- 2026-06-04: disclosed: CVE-2026-10951 published.

## References

- [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html)
- [https://issues.chromium.org/issues/505191883](https://issues.chromium.org/issues/505191883)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)