Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Local vector and required user interaction match file-based trigger; C:H reflects password data exposure; no integrity or availability impact applies.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Passwords in Google Chrome on Mac prior to 150.0.7871.47 allowed a local attacker to obtain potentially sensitive information from process memory via a malicious file. (Chromium security severity: Medium)
AnalysisAI
Chrome's built-in Passwords subsystem on macOS leaks sensitive process memory contents when a malicious file is processed, potentially exposing stored credentials or authentication tokens to a local attacker. All Google Chrome releases for Mac prior to 150.0.7871.47 are affected. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in CISA KEV; however, the confidentiality impact is rated High given the nature of the data at risk within the Passwords feature.
Technical ContextAI
CWE-284 (Improper Access Control) identifies the root cause as a failure to properly restrict access to sensitive memory regions within Chrome's Password manager component on macOS. The 'inappropriate implementation' phrasing used by Google typically denotes logic or design errors - in this case likely insufficient memory isolation, improper scoping of credential buffers, or failure to sanitize sensitive values after use within the Passwords subsystem. The vulnerability is Mac-specific, suggesting it is tied to platform-level file handling APIs or macOS-specific IPC/memory mechanisms that interact with Chrome's password storage layer. When a specially crafted file is opened, it appears to trigger a code path that exposes in-memory credential data beyond its intended scope.
RemediationAI
The primary fix is to update Google Chrome on macOS to version 150.0.7871.47 or later, which contains the vendor-released patch per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Updates can be applied via Chrome's built-in auto-update mechanism (Help > About Google Chrome) or by downloading the latest release directly from Google. As a compensating control prior to patching, avoid opening untrusted files while Chrome is running with an active saved-password session; additionally, consider temporarily disabling Chrome's built-in password manager (chrome://settings/passwords) in favor of a standalone password manager to reduce the attack surface - note that doing so removes autofill and credential synchronization functionality.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
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
EUVD-2026-40600
GHSA-hp82-6qcx-x2xc