Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Passwords in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Cross-origin data leakage in Google Chrome's Passwords feature (all versions prior to 149.0.7827.103) can be triggered by a remote unauthenticated attacker delivering a crafted HTML page to a victim. The flaw results from an inappropriate implementation classified under CWE-693 (Protection Mechanism Failure), meaning the browser's same-origin policy enforcement is bypassed specifically within the Passwords subsystem. With a CVSS score of 4.3 and no public exploit or CISA KEV listing identified at time of analysis, this is a medium-severity information disclosure risk requiring user interaction to exploit.
Technical ContextAI
The vulnerability resides in the Passwords component of the Chromium browser engine, which handles autofill, credential storage, and password-related UI behaviors. CWE-693 (Protection Mechanism Failure) indicates the root cause is a failure to correctly apply or enforce a security protection mechanism - in this context, the Same-Origin Policy (SOP), which is the browser's foundational isolation boundary between web origins. An 'inappropriate implementation' in the Passwords subsystem inadvertently exposes data that should be scoped to a single origin, making it readable by a cross-origin page. The affected CPE corresponds to Google Chrome prior to 149.0.7827.103 on desktop platforms, as confirmed by the EUVD advisory (EUVD-2026-35221) and Google's stable channel release notes.
RemediationAI
The primary fix is to update Google Chrome to version 149.0.7827.103 or later via the browser's built-in update mechanism (chrome://settings/help) or enterprise deployment tooling. The patch is confirmed available from the vendor per the stable channel advisory at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html. No workaround fully addresses the root cause; however, organizations that cannot immediately deploy the patch may reduce exposure by disabling Chrome's built-in password manager (chrome://settings/passwords → turn off 'Offer to save passwords' and 'Auto sign-in') - note this removes autofill functionality and shifts credential management responsibility to users or a third-party manager. Browser isolation policies (e.g., enforcing Site Isolation via enterprise policy SitePerProcess) may reduce cross-origin data exposure as a defense-in-depth measure but are not a confirmed mitigation for this specific flaw.
Same weakness CWE-693 – Protection Mechanism Failure
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-35221
GHSA-q4rm-h6xg-hcmq