Open VSX Registry does not sanitize SVG files uploaded as extension icons prior to storage, and serves them with Content-Type: image/svg+xml without security headers such as Content-Security-Policy or Content-Disposition: attachment. This allows an attacker to publish an extension with a malicious SVG icon and achieve stored cross-site scripting (XSS) when a user navigates directly to the icon URL. On deployments using local storage, script execution occurs within the Open VSX application origin, enabling session hijacking, authentication token theft, and unauthorized extension publishing. On deployments backed by external storage (such as open-vsx.org with an S3-backed CDN), execution is confined to the storage origin, reducing impact but still permitting phishing attacks and credential harvesting through attacker-crafted pages.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/91 Issue Tracking, Vendor Advisory, Exploit
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.4 · eclipseNVD modified 2026-10-25 23:10
Affected (CPE criteria) 1
cpe:2.3:a:eclipse:open_vsx:*:*:*:*:*:*:*:*
References 1
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/91 Issue Tracking, Vendor Advisory, Exploit