Quick answers
- Is CVE-2026-10896 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10896 being exploited in the wild.
- How severe is CVE-2026-10896?
- Informational severity, with a CVSS score of 9.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-10896?
- A patch was published on 2026-06-02: Fixed in version 149.0.7827.53 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-10896 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-10896?
- 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 incorrectly manages memory during the processing of HTML content, allowing a remote attacker to leverage a crafted HTML page to corrupt memory. This can lead to arbitrary code execution (ACE) within the context of the browser process. The vulnerability was reported by Google internally and is addressed in version 149.0.7827.53. While the CVSS score was not provided in the advisory, Chromium has assigned it a 'Critical' severity rating, which typically corresponds to high-impact remote code execution.
Affected products
- Google Chrome for iOS prior to 149.0.7827.53
Timeline
- 2026-05-15: disclosed: Reported by Google internal researchers
- 2026-06-02: patched: Fixed in version 149.0.7827.53
- 2026-06-04: advisory