CVE-2026-13323: XSS
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-13323?
The severity of CVE-2026-13323 is medium, rated at 4.1.
How do I fix CVE-2026-13323?
To fix CVE-2026-13323, update to Open VSX Registry version 1.0.2 or higher.
What types of attacks are possible due to CVE-2026-13323?
CVE-2026-13323 allows unauthenticated attackers to upload malicious VSIX files leading to potential cross-site scripting (XSS) attacks.
Is user authentication required to exploit CVE-2026-13323?
No, CVE-2026-13323 can be exploited by unauthenticated attackers.
What is the potential impact of CVE-2026-13323?
The potential impact of CVE-2026-13323 includes execution of arbitrary scripts in a user's context, leading to data exposure and unauthorized actions.