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