Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost crafted HTML page
-
DeliverySocial-engineer victim to visit page
-
ExploitVictim performs UI gesture (e.g., drag-and-drop)
-
ExecutionDataTransfer API bypasses origin validation
-
PersistCross-origin data exposed to attacker page
-
ImpactExfiltrate leaked data to attacker server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
|
| Exploitation Conditions | Exploitation requires that the victim is running Google Chrome prior to version 151.0.7922.72 on a desktop platform. The victim must be convinced to visit an attacker-controlled or attacker-influenced HTML page AND perform specific UI gestures while on that page - such as a drag-and-drop interaction - which is the key limiting condition explicitly stated in the CVE description. The CVSS UI:R metric confirms this user interaction is non-negotiable; passive browsing without interaction is not sufficient to trigger the flaw. The CVSS PR:N metric confirms no authentication or account on the target system is required from the attacker's perspective. Exploitation is further limited to scenarios where cross-origin data is accessible in the same browser session (e.g., another open tab or an embedded iframe) at the time the gesture occurs. No special server-side configuration or non-default Chrome settings are required. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N presents a baseline medium risk: the attack is network-delivered with no authentication requirement, but the mandatory user interaction (UI:R) is a meaningful barrier. The confidentiality impact is limited (C:L), with no integrity or availability consequences. The EPSS score of 0.18% at the 8th percentile strongly suggests this vulnerability is not being actively targeted in the wild, and the absence of a CISA KEV listing corroborates this. No POC code has been identified. Taken together, this is a real but low-urgency vulnerability: the primary risk comes from Chrome's ubiquitous deployment, meaning even a low-probability exploit scenario could reach millions of users. The user interaction prerequisite limits the threat to social-engineering attacks - phishing, malvertising, or malicious embeds - rather than opportunistic mass exploitation. This is a patch-and-move-on issue rather than an emergency response trigger. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page that embeds or references cross-origin content and is designed to trigger specific UI interactions - such as a user dragging an element - which invokes the vulnerable DataTransfer code path. The attacker distributes the link via phishing or malvertising to Chrome users running versions below 151.0.7922.72. When a victim visits the page and performs the prompted gesture, the browser leaks data from a cross-origin context (such as content from another tab or an embedded iframe from a different domain) to the attacker-controlled page, which can then exfiltrate it. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Cross-origin data leakage in Google Chrome's DataTransfer API implementation (prior to 151.0.7922.72) allows a remote unauthenticated attacker to read sensitive data from a different origin when a victim performs specific UI gestures - such as drag-and-drop interactions - on a crafted HTML page. The vulnerability is rated CVSS 4.3 (Medium) with an EPSS probability of just 0.18% (8th percentile), indicating very low observed exploitation activity. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV, but Chrome's widespread deployment makes even medium-severity browser flaws worth prioritizing for rapid patching.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, which includes the fix for this DataTransfer origin validation error. The vendor patch is confirmed available via the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome's auto-update mechanism will apply this fix automatically in most managed and consumer environments; verify deployment via browser version strings in endpoint management tooling. For environments where immediate patching is not possible, organizations can reduce exposure by enforcing web content filtering to block access to untrusted or unknown HTML pages, reducing the attack surface for the required UI gesture interaction. Restricting drag-and-drop functionality via Group Policy (ChromeDragAndDropEnabled) in enterprise environments is a targeted compensating control, though it may impair legitimate productivity workflows. Chromium-derivative browsers should be tracked independently for their own patch releases.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in Chrome's DataTransfer API implementation, used to move data between drag-and-drop sources and targets or between clipboard operations. CWE-346 (Origin Validation Error) identifies the root cause: Chrome failed to properly enforce same-origin policy boundaries when a DataTransfer operation crossed origins, allowing data from one origin to be exposed to a page on a different origin. This class of flaw typically arises when browser internal state for clipboard or drag-and-drop objects is shared or insufficiently sandboxed between browsing contexts. The affected product is identified via CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, encompassing all Chrome desktop versions prior to 151.0.7922.72 across Windows, macOS, and Linux. The EUVD entry EUVD-2026-50644 corroborates the affected version range as all Chrome builds below 151.0.7922.72.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Network-delivered via crafted page (AV:N), no privileges required (PR:N), but mandatory user UI gesture (UI:R); only limited cross-origin confidentiality leak, no integrity or availability impact.
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 who convinced a user to engage in specific UI gestures to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Google Chrome 151 Security Vulnerabilities
View all 80Same weakness CWE-346 – Origin Validation Error
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 |
EUVD-2026-50644
GHSA-ff3f-6wm3-vj2m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB