EUVD-2026-40560
GHSA-4hqp-vpr6-3wc9
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Race condition demands precise timing control (AC:H); user must actively trigger DataTransfer (UI:R); impact is read-only memory disclosure within renderer scope (C:H, I:N, A:N, S:U).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Race in DataTransfer in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Race condition in the DataTransfer API in Google Chrome prior to 150.0.7871.47 allows a remote attacker to read potentially sensitive data from renderer process memory by luring a user to a specially crafted HTML page. The CVSS vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N) confirms the impact is limited to confidentiality - no integrity or availability loss - and that reliable exploitation requires winning a timing race (AC:H) combined with user interaction. No public exploit identified at time of analysis; Google has shipped a patch in the stable channel update dated June 2026.
Technical ContextAI
The vulnerability resides in Chrome's DataTransfer implementation, the internal subsystem that brokers clipboard and drag-and-drop data between web content and the browser host. CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization) identifies the root cause as a classic race condition: two execution contexts - likely a JavaScript event handler and an internal browser thread managing DataTransfer state - access shared memory without adequate synchronization primitives (mutex, lock, or atomic check). This creates a time-of-check/time-of-use (TOCTOU) window during which an attacker-controlled page can read memory contents that should have been cleared or restricted. Because the scope is unchanged (S:U), exploitation is bounded to the renderer process address space and does not constitute a sandbox escape. The affected version range, per EUVD-2026-40560, is any Chrome release below 150.0.7871.47.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later, as documented in the stable channel release at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. End users can trigger an immediate update via Chrome menu > Help > About Google Chrome. Enterprise administrators should deploy the update via Google Admin Console, Intune, or their MDM platform, prioritizing workstations used for sensitive data handling. No practical in-product workaround exists to neutralize a race condition in DataTransfer without disabling core browser functionality; however, Chrome's Site Isolation (enabled by default) already limits the blast radius of renderer-level memory disclosure to the affected site's process. Organizations with high-risk user populations may consider enforcing a browser update SLA of 48-72 hours for medium-severity Chrome issues to contain potential targeted use.
Same weakness CWE-362 – Race Condition
View allSame 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