EUVD-2026-34724
GHSA-qq6v-fw2p-f39m
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient policy enforcement in WebAuthentication in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Cross-origin data leakage in Google Chrome for Android prior to 149.0.7827.53 exposes sensitive information through insufficient policy enforcement in the WebAuthentication (WebAuthn) component. An attacker who has already achieved renderer process compromise can exploit this gap to extract cross-origin data by delivering a crafted HTML page to a victim, requiring user interaction. No public exploit has been identified at time of analysis, and EPSS places exploitation probability at a low 0.05% (16th percentile), consistent with Google's own 'Low' severity classification for Chromium.
Technical ContextAI
The vulnerability resides in the WebAuthentication (WebAuthn) subsystem of Google Chrome on Android, tracked under CWE-693 (Protection Mechanism Failure). WebAuthn is a W3C standard for credential-based authentication using public-key cryptography; its implementation in Chrome enforces cross-origin isolation policies to prevent one origin from accessing another's authentication data. The flaw represents a failure in that enforcement boundary - specifically, a policy that should restrict cross-origin data access is not consistently applied when the renderer is in a compromised state. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) reflects a network-reachable, low-complexity attack requiring only a user visit to a crafted page, though the description introduces a significant unstated prerequisite: prior renderer process compromise, which implies a chained exploitation scenario rather than a standalone attack.
RemediationAI
Update Google Chrome on Android to version 149.0.7827.53 or later, the vendor-released patch documented at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. On Android, updates are delivered via the Google Play Store; enterprise environments using managed Chrome (via Google Admin or EMM) should push the update through their device management policy. Because exploitation requires prior renderer process compromise, reducing the renderer attack surface through Chrome's Site Isolation feature (enabled by default on modern Android Chrome builds) provides a meaningful compensating control - maintaining or enforcing Site Isolation limits the blast radius of any renderer compromise that might enable this secondary leak. There are no known workarounds that directly address the WebAuthentication policy gap without updating.
Same weakness CWE-693 – Protection Mechanism Failure
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today