Severity by source
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Network delivery via crafted page requires active user visit (UI:R); cross-origin data leak is partial (C:L); no integrity, availability, or scope-change impact applies.
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
4DescriptionCVE.org
Inappropriate implementation in DataTransfer in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Cross-origin data leakage in Google Chrome prior to 151.0.7922.72 allows remote attackers to read sensitive data from other origins by luring a victim to a crafted HTML page that abuses an inappropriate implementation in the DataTransfer API. The impact is limited to partial confidentiality loss (C:L) with no integrity or availability effects, and Chromium's own security team rated this Low severity. No public exploit code or active exploitation has been identified at time of analysis; EPSS probability of exploitation is very low at 0.17% (7th percentile).
Technical ContextAI
The DataTransfer API in Chromium is the browser interface that manages data transferred during drag-and-drop operations and clipboard interactions between web content. An inappropriate implementation in this component permits a crafted page to access data that originates from a different security origin, violating the browser's Same-Origin Policy boundary. The root cause class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), indicating that access controls on the DataTransfer object fail to prevent cross-origin reads under specific conditions. The affected product is Google Chrome as identified by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, all versions prior to 151.0.7922.72 on desktop platforms.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, which contains the vendor-released fix per the stable channel update advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome's auto-update mechanism will deliver this patch automatically in most managed and consumer environments; administrators should verify deployment via policy dashboards. No confirmed workaround is documented. If immediate patching is not possible, reducing exposure to untrusted HTML content (e.g., restricting browsing to allowlisted domains via enterprise policy) would reduce the attack surface, though this has operational trade-offs for general-purpose browsing environments.
Same weakness CWE-200 – Information Exposure
View allSame 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
EUVD-2026-50854
GHSA-w298-fwph-8fhx