EUVD-2026-50600
GHSA-gvh4-9j76-m35h
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects the mandatory renderer-compromise prerequisite; remaining metrics align with the vendor description and published vector.
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: Chrome
Lifecycle Timeline
5DescriptionCVE.org
Side-channel information leakage in Autofill in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Side-channel information leakage in Chrome's Autofill component exposes cross-origin data to remote attackers who have already achieved renderer process compromise. All Chrome versions prior to 151.0.7922.72 are affected across all platforms. With an EPSS of 0.22% (12th percentile), no CISA KEV listing, and a mandatory renderer-compromise prerequisite, real-world exploitation risk is substantially lower than the CVSS base score implies - this is a chained second-stage disclosure, not a standalone attack. No public exploit identified at time of analysis.
Technical ContextAI
The vulnerability resides in Chrome's Autofill subsystem and is classified under CWE-1300 (Improper Protection of Physical Side Channels). Side-channel attacks exploit observable differences in timing, memory access patterns, or resource consumption rather than direct memory corruption, allowing inference of sensitive data without direct access. In this case, the Autofill feature - which stores and surfaces form field data - leaks cross-origin information through measurable side effects accessible from a compromised renderer context. The CPE string cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* confirms all Chrome builds prior to 151.0.7922.72 are within scope. Chrome's multi-process architecture and site isolation are relevant mitigating structures, but a pre-compromised renderer can still observe side-channel signals across origin boundaries via the Autofill interface.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, which contains the vendor-released patch for this vulnerability. The stable channel update is detailed at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Most consumer and enterprise Chrome deployments update automatically; administrators managing fleets should verify all endpoints are running 151.0.7922.72 or later using endpoint management tooling. No documented workaround isolates the Autofill side-channel specifically. Given the renderer-compromise prerequisite, organizations should also prioritize hardening against renderer exploits broadly - for example, enabling Chrome's Enhanced Safe Browsing, enforcing renderer sandbox policies via enterprise policy, and ensuring timely patching of all Chrome releases to reduce the likelihood of the prerequisite renderer compromise being achievable.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today