CVE-2026-4983: XSS

Published Jun 23, 2026
·
Updated

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.

Affected Software

2 affected components
Eclipse Foundation Open VSX Registry
Eclipse Open VSX>=0.1.0<0.34.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Serve SVG icon files with the HTTP header Content-Disposition: attachment to force download rather than in-browser rendering of the SVG.

    Open VSX Registry HTTP responses for extension icons Content-Disposition = attachment
  2. Configuration

    Sanitize uploaded SVG files prior to storage: remove <script> elements, on* event handler attributes, external resource references and other active content before saving icons.

    Open VSX Registry (icon upload pipeline) svg_sanitization = enabled
  3. Compensating control

    Serve extension SVG icon responses with a restrictive Content-Security-Policy that prevents script execution and loading of external resources for SVG responses (i.e., add a CSP on SVG responses to disallow scripts and external sources).

  4. Operational

    Locate existing stored SVG icon files in the registry/storage, and re-scan each file; sanitize or remove any SVGs containing scripts or active content and replace with sanitized copies or remove the icon completely.

Event History

Jun 23, 2026
CVE Published
via MITRE·10:50 AM
Data Sourced
via MITRE·10:50 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-4983?

CVE-2026-4983 has a medium severity rating of 4.1.

2

What type of vulnerability is represented by CVE-2026-4983?

CVE-2026-4983 is classified as an XSS (Cross-Site Scripting) vulnerability.

3

How does CVE-2026-4983 impact the Open VSX Registry?

CVE-2026-4983 allows attackers to upload malicious SVG files as extension icons, potentially enabling code execution.

4

How can I mitigate CVE-2026-4983?

Mitigating CVE-2026-4983 involves sanitizing uploaded SVG files and implementing appropriate security headers.

5

What is the vector for exploitation in CVE-2026-4983?

CVE-2026-4983 can be exploited remotely through the upload of unvalidated SVG files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203