Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Cross-origin data leakage crosses the same-origin security boundary (S:C); no privileges required and user must only visit the attacker's page.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Side-channel information leakage in Scroll in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Side-channel information leakage via Chrome's Scroll implementation exposes cross-origin data to remote attackers who can lure a victim to a crafted HTML page. All Chrome versions prior to 150.0.7871.47 are affected; exploitation requires user interaction (visiting the attacker-controlled page) but no authentication. No public exploit identified at time of analysis and EPSS sits at the 11th percentile, though the confidentiality impact is rated High by NVD given the potential to read data from foreign origins.
Technical ContextAI
CWE-1300 (Improper Protection of Physical Side Channels) is applied here in a browser behavioral context: Chrome's Scroll implementation leaks observable differences - likely timing, layout geometry, or scroll-position inference - that allow a page in one origin to deduce content or state from a cross-origin frame or resource. This class of vulnerability exploits the browser's own internal rendering or event-handling subsystem as an unintentional covert channel. The affected component is Google Chrome (Chromium engine) in all releases prior to the 150.0.7871.47 stable channel build, as identified in the Chrome releases advisory and the EUVD entry EUVD-2026-40476. No CPE strings were provided in the source data, but the affected scope is the Chromium browser across desktop platforms.
RemediationAI
Vendor-released patch: Chrome 150.0.7871.47. Update immediately via Chrome's built-in updater (Settings → Help → About Google Chrome) or via enterprise deployment tooling; the advisory is at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. For organizations that cannot immediately update, compensating controls include enforcing Chrome's Site Isolation feature (--site-per-process, enabled by default in modern Chrome) which raises the bar for cross-origin side-channel attacks, and restricting user access to untrusted or unknown web properties via proxy policy. Disabling JavaScript entirely would prevent exploitation but is operationally impractical for most deployments. Enterprise administrators should prioritize patching given Chrome's ubiquitous deployment footprint, even though real-world exploitation signals remain low.
Same 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
EUVD-2026-40476
GHSA-28x5-j68m-fxr3