# CVE-2026-18011: Google Chrome for iOS information disclosure in process memory

Source: https://junglewise.ai/threats/cve-2026-18011-google-chrome-for-ios-information-disclosure-in-process-memory  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-30. Updated: 2026-07-30  
License: CC BY 4.0 with a link back

CVE-2026-18011 · Severity: info · Published 2026-07-30

Google Chrome for iOS is a mobile web browser used to access the internet on Apple devices. A security flaw in this application could allow an individual with physical access to a user's device to extract sensitive information from the browser's active memory. This could potentially lead to the exposure of private data handled during a browsing session.

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

## Quick answers

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

**How severe is CVE-2026-18011?** Informational severity, published 30 July 2026.

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

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

**How is CVE-2026-18011 attacked?** It is attacked with physical access, in a network appliance.

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

An information disclosure vulnerability exists in Google Chrome for iOS due to an inappropriate implementation within the application's process handling. The vulnerability allows a local attacker who has physical access to an unlocked device to read sensitive information directly from the application's process memory. This is classified by Chromium as a low-severity issue because it requires physical proximity and access to the hardware. The issue was addressed in version 151.0.7922.72.

## Affected products

- Google Chrome for iOS prior to 151.0.7922.72

## Timeline

- 2026-07-29: patched: Fixed in version 151.0.7922.72
- 2026-07-30: disclosed

## References

- [https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html](https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html)
- [https://issues.chromium.org/issues/522479633](https://issues.chromium.org/issues/522479633)

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