Physical process-memory disclosure
Published Jul 30, 2026 · Updated Jul 30, 2026
Information disclosure in Google Chrome for iOS before 151.0.7922.72 allows physically proximate attackers to read process memory. Google describes the affected locus only as Chrome for iOS and has not published the incorrect operation that exposes memory. Physical access to the iOS device is required, and the documented consequence is limited to disclosure without data modification or service interruption.
Summary
What happened
Information disclosure in Google Chrome for iOS before 151.0.7922.72 allows physically proximate attackers to read process memory. Google describes the affected locus only as Chrome for iOS and has not published the incorrect operation that exposes memory. Physical access to the iOS device is required, and the documented consequence is limited to disclosure without data modification or service interruption.
The record
- CVE
- CVE-2026-18011
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=151.0.7922.72 <151.0.7922.72
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo