Open VSX Bug Let Malicious VS Code Extensions Bypass Pre-Publish Security Checks
Summary: Koi Security researcher Oran Simhony disclosed a now-patched bug in Open VSX's pre-publish scanning pipeline where a single boolean return value meant both 'no scanners are configured' and 'all scanners failed to run,' so failed scans were treated as nothing to scan and malicious VS Code extensions passed vetting. An attacker with only a free publisher account could flood the publish endpoint with malicious .VSIX extensions to exhaust the database connection pool, and a recovery service meant to retry failed scans shared the same flaw; the issue was fixed in Open VSX version 0.32.0 following responsible disclosure on February 8, 2026.
Bottom line: Open VSX also serves as the extension marketplace for Cursor, Windsurf, and other VS Code forks, so a gate that opened under load exposed every one of those users to extensions that were never scanned - and it took nothing more than a free publisher account to trigger it.
Read the original at The Hacker News ↗