Severity by source
AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Network delivery via crafted HTML page justifies AV:N; PR:L reflects authenticated context needed for cross-origin leakage; UI:R for required victim interaction; C:L for limited data exposure only.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
5DescriptionCVE.org
Inappropriate implementation in Editing in Google Chrome on Linux 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 on Linux (prior to 151.0.7922.72) stems from an inappropriate implementation in the browser's Editing subsystem, enabling a remote attacker to exfiltrate limited cross-origin information when a victim interacts with a crafted HTML page. The CVSS vector (PR:L/UI:R) confirms exploitation requires both some authenticated context and active victim interaction, materially reducing opportunistic risk. No public exploit has been identified and EPSS sits at the 7th percentile, consistent with the vendor's own 'Low' severity classification.
Technical ContextAI
The vulnerability resides in Chromium's Editing component - the subsystem responsible for clipboard operations, text selection, drag-and-drop, and contenteditable handling - specifically on the Linux platform. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) identifies the root cause as a failure to enforce information boundaries: the editing subsystem improperly permits cross-origin data to become observable to an attacker-controlled page, violating the Same-Origin Policy. This is a platform-specific defect; the CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) applies broadly but the description explicitly scopes impact to Linux. The Chromium issue tracker entry (https://issues.chromium.org/issues/497251066) is the upstream reference for the root-cause defect.
RemediationAI
Update Google Chrome on Linux to version 151.0.7922.72 or later via the stable channel, as detailed in the vendor advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome's built-in auto-update mechanism will apply this for most end users; enterprise deployments using managed policies should confirm the update has propagated. As a compensating control prior to patching, enabling Chrome's Strict Site Isolation (chrome://flags/#enable-site-per-process) can limit cross-origin data exposure by isolating renderer processes per origin, though this may increase memory usage. Given the Low severity, PR:L requirement, and user-interaction dependency, this fix is appropriate for inclusion in the next standard patch cycle rather than emergency deployment.
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-50651
GHSA-3wq4-w788-rhg3