mediumCVE-2026-13323

CVE-2026-13323 Eclipse Open VSX HTML Rendering Supply Chain Vulnerability

In Open VSX Registry before 1.0.2, the /vscode/unpkg/ endpoint serves user-supplied HTML files with Content-Type: text/html and without a Content-Security-Policy or Content-Disposition: attachment response header. An unauthenticated attacker can register a publisher account, upload a VSIX containing a crafted HTML payload, and induce an authenticated user to visit the resulting URL. The browser renders the file inline in the open-vsx.org origin context, enabling session token exfiltration, persistent Personal Access Token (PAT) generation, and unauthorized publication of malicious extension versions. Because Open VSX extensions are distributed to VS Code, VSCodium, Cursor, Windsurf, and compatible editors, a compromised extension update constitutes a supply chain attack against all downstream users.

ProductEclipse Open VSX
CVSS4.1
EPSSNot scored yet
UpdatedJuly 15, 2026

Quick answer

Eclipse Foundation Eclipse Open VSX should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • < 1.0.2

Fixed versions

  • 1.0.2

How to fix it

Eclipse Open VSX is affected by this security issue. The safest fix is to update to the fixed version, then test the site or service again to make sure the risky path is closed.

  1. Find every place where Eclipse Open VSX is installed or used.
  2. Update to 1.0.2 or a later vendor-supported version.
  3. Back up the site or service before changing production systems.
  4. Apply the update in staging first if possible, then deploy it to production.
  5. If you cannot update right away, restrict access to the affected feature and monitor logs closely.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version is no longer in the affected range.
  • Retest the affected page, API, upload, login, chat, container, or network flow.
  • Check logs after the change for blocked attempts, crashes, or errors.
  • Run a fresh Fixnx scan and save the report.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-13323?

Eclipse Foundation Eclipse Open VSX versions listed as affected should be reviewed: < 1.0.2.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.