Open VSX Extension Possession Supply Chain Vulnerability
Score: 8/10

Open VSX Extension Possession Supply Chain Vulnerability

Researchers identified a stored XSS vulnerability in Open VSX that allows attackers to hijack extension maintainer accounts and distribute malicious updates to millions of developers.

Executive Summary

Security researchers at Bloom Security discovered a critical stored XSS vulnerability, tracked as CVE-2026-13323, affecting the Open VSX registry—the backend for popular IDEs like Cursor, Windsurf, and VSCodium. The vulnerability allows an attacker to publish a malicious extension containing an HTML payload that, when viewed by a logged-in maintainer, can silently mint persistent Personal Access Tokens (PATs) in the maintainer's name.

Technically, the attack chain exploits the registry's failure to implement proper security headers (CSP, X-Content-Type-Options, Content-Disposition) on its file-serving endpoint (/vscode/unpkg/). This allows for session hijacking via a single-click link, leading to the unauthorized publication of malicious extension versions. Because most VS Code forks enable extension auto-updates by default, a single compromise can reach millions of developer machines within 24 hours.

This represents a significant supply-chain threat to the software development sector, as it weaponizes the trust relationship between developers and the open-source tools they rely on. While the CVEs have been patched in Open VSX 1.0.2, the incident highlights a broader shift in adversary tradecraft toward targeting the developer delivery mechanism.

Key Details

Threat Name

CVE-2026-13323

Affects

Open VSX, VSCodium, Cursor, Windsurf

Adversary

—

Malware/Tools

Shai-Hulud

Report Score

8out of 10
Quality Score
Good
IOC Quality4
TTP Details9
Detection Guidance6
Enterprise Relevance9
Clarity & Structure9
Technical Depth8

Sources