# CVE-2026-13813: Google Chrome for iOS sandbox escape in renderer process

Source: https://junglewise.ai/threats/cve-2026-13813-google-chrome-for-ios-sandbox-escape-in-renderer-process  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-30. Updated: 2026-06-30  
License: CC BY 4.0 with a link back

CVE-2026-13813 · Severity: info · CVSS 8.8 · Published 2026-06-30

Google Chrome for iOS is a mobile web browser used to access the internet on Apple devices. A security vulnerability in versions prior to 150.0.7871.47 could allow a malicious website to bypass the browser's security boundaries (sandbox). If exploited, this could allow an attacker to gain unauthorized access to the device's system or data beyond what a normal website should be able to reach.

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

## Quick answers

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

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

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

**Is there a fix for CVE-2026-13813?** A patch was published on 2026-06-30: Fixed in version 150.0.7871.47 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-13813?** 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

This vulnerability is classified as insufficient policy enforcement (CWE-20) within the Chrome for iOS component. The flaw allows a remote attacker to achieve a sandbox escape if they have already compromised the renderer process. By enticing a user to visit a specially crafted HTML page, the attacker can bypass security restrictions intended to isolate the browser process from the underlying operating system. The issue was addressed in version 150.0.7871.47. While the advisory lists the severity as 'High' and mentions renderer compromise as a precondition, the impact of a sandbox escape typically allows for broader system access.

## Affected products

- Google Chrome for iOS prior to 150.0.7871.47

## Timeline

- 2026-05-01: disclosed: Reported to Chromium by Google researchers
- 2026-06-30: patched: Fixed in version 150.0.7871.47
- 2026-06-30: advisory

## References

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

## 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)