EUVD-2026-40704
GHSA-v8xp-pp2f-88gh
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network-delivered via crafted page (AV:N), no attacker privileges needed (PR:N), but victim must visit the page (UI:R); impact is confidentiality-only with no write or availability consequence.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in SVG in Google Chrome prior to 150.0.7871.47 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 prior to version 150.0.7871.47 allows a remote attacker to read data from cross-origin resources by luring a victim to a crafted HTML page. The flaw exploits improper SVG handling that bypasses same-origin policy protections, exposing potentially sensitive session data or authenticated content from third-party origins. No active exploitation has been confirmed (not listed in CISA KEV), and EPSS stands at 0.17% (7th percentile), indicating low observed exploitation probability at time of analysis.
Technical ContextAI
The vulnerability resides in Chrome's SVG (Scalable Vector Graphics) rendering engine. SVG natively supports cross-origin resource embedding and external references, and an inappropriate implementation in how Chrome processed SVG content allowed these references to leak response data across origin boundaries, violating the browser same-origin policy. The CWE-352 (Cross-Site Request Forgery) classification is notable and somewhat inconsistent with the described SVG data-leak primitive - CSRF typically describes forged authenticated requests rather than passive response reading. This may reflect a mechanism where the SVG engine performs implicit cross-origin requests whose responses are accessible to the attacker's origin, combining CSRF-like request forgery with a same-origin policy bypass. Affected versions are all Chrome desktop releases prior to 150.0.7871.47 across all supported platforms.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later, which is the vendor-confirmed patched release per the stable channel advisory at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome auto-updates by default; users and administrators should confirm the current version via chrome://settings/help. Enterprises managing Chrome via Google Admin Console or MDM solutions should enforce a minimum version policy of 150.0.7871.47. As a short-term compensating control prior to patching, organizations can block navigation to untrusted external URLs through web proxy policies or restrict use of inline SVG in proxied content - though both carry significant usability trade-offs in modern web environments. Disabling JavaScript entirely would neutralize the crafted-page delivery vector but is not operationally viable for most deployments.
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
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