Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
AV:N for web-delivered exploit; AC:H for unspecified browser state prerequisites; PR:N since no attacker account needed; UI:R for required victim page visit; C:L for partial cross-origin data leak only.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in SVG 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: Medium)
AnalysisAI
Cross-origin data leakage in Google Chrome's SVG implementation (all versions prior to 151.0.7922.72) enables remote attackers to read data from cross-origin resources by luring a victim to a crafted HTML page. The flaw, rooted in an origin validation error (CWE-346) in Chrome's SVG rendering engine, breaks same-origin policy protections. No public exploit identified at time of analysis; EPSS at 0.21% (11th percentile) and SSVC exploitation status of 'none' collectively indicate low near-term exploitation probability.
Technical ContextAI
The vulnerability exists in Google Chrome's SVG (Scalable Vector Graphics) rendering subsystem, which is part of the Blink rendering engine embedded in Chromium. SVG elements natively support cross-origin resource references (e.g., image, filter, use elements pointing to external URIs), and an inappropriate implementation in Chrome's SVG handling failed to correctly enforce origin validation per CWE-346 (Origin Validation Error). This class of flaw allows attacker-controlled SVG constructs to observe or extract data from cross-origin contexts that the same-origin policy is meant to isolate. CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* confirms all Chrome releases prior to 151.0.7922.72 carry this flaw across all platforms.
RemediationAI
Upgrade Google Chrome to version 151.0.7922.72 or later, as documented in the Chrome Stable Channel Update advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html). Chrome typically auto-updates silently; users can verify and trigger an update manually via the browser menu at Help > About Google Chrome. Enterprise administrators should ensure managed Chrome deployments are enrolled in a channel that has received the 151.0.7922.72 stable update. If immediate patching is not feasible, reducing exposure to untrusted web content via enterprise browser policies (e.g., restricting navigation to allowlisted domains) would reduce attack surface, though this trades significant usability impact for a low-severity information disclosure risk.
Same weakness CWE-346 – Origin Validation Error
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-50679
GHSA-q7gj-pj54-2g7f