Quick answers
- Is CVE-2026-10952 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10952 being exploited in the wild.
- How severe is CVE-2026-10952?
- 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-10952?
- A patch was published on 2026-06-02: Chrome 149 promoted to stable channel. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-10952 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-10952?
- 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 iOS-specific implementation of Google Chrome. The flaw is triggered when the browser attempts to access memory that has already been deallocated, typically during the processing of specially crafted HTML content. A remote, unauthenticated attacker can exploit this by enticing a user to visit a malicious website, leading to heap corruption. This can result in a stable browser crash (Denial of Service) or potentially arbitrary code execution within the sandbox context of the browser. The issue is resolved in version 149.0.7827.53.
Affected products
- Google Chrome for iOS prior to 149.0.7827.53
Timeline
- 2026-06-02: patched: Chrome 149 promoted to stable channel.
- 2026-06-04: disclosed: CVE published to NVD.