EUVD-2026-40494
GHSA-v598-mr98-5866
Severity by source
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Physical device presence is the sole access requirement (AV:P); no credential or privilege needed; only confidentiality impacted via in-process memory read.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient data validation in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 allowed a local attacker to obtain potentially sensitive information from process memory via physical access to the device. (Chromium security severity: High)
AnalysisAI
Sensitive process memory exposure in Google Chrome for iOS prior to 150.0.7871.47 enables a physically present attacker to read potentially sensitive data from the browser's memory without authentication. The root cause is insufficient data validation (CWE-20) within the iOS-specific Chrome implementation. No public exploit code or CISA KEV listing has been identified at time of analysis, and the physical access requirement (CVSS AV:P) significantly constrains real-world attacker opportunity.
Technical ContextAI
The vulnerability resides in Chrome for iOS - Google's Chromium-based browser packaged for Apple's iOS platform - prior to version 150.0.7871.47. CWE-20 (Improper Input Validation) as the root cause class indicates that Chrome for iOS fails to adequately validate or sanitize data in a code path accessible under physical access conditions, resulting in unintended leakage of in-process memory contents. This is distinct from Chrome's desktop codebase; iOS imposes sandboxing constraints that shape both the attack surface and exploitation pathway. The memory disclosure could expose session tokens, cached credentials, form data, or other sensitive browser state depending on what the process holds at time of exploitation.
RemediationAI
Update Google Chrome for iOS to version 150.0.7871.47 or later via the Apple App Store. The vendor-released patch is confirmed available per the Chrome stable channel advisory (chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). Organizations managing iOS fleets via MDM should push the update and verify installed Chrome version compliance. As a compensating control where immediate patching is not possible, restricting physical access to devices containing sensitive browsing sessions - through device lock policies, screen timeout enforcement, and full-disk encryption - reduces the realistic exploitation window. Enabling iOS Lockdown Mode for high-risk users adds an additional layer of process isolation.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today