When Your IDE Becomes a RCE Endpoint
Researchers have discovered a vulnerability in the OpenVSX registry that allows attackers to execute code on developers' machines through VS Code-derived editors. The vulnerability is due to a dependency confusion problem, where an attacker can register an abandoned or never claimed publisher extension namespace on OpenVSX and have every Cursor, Windsurf, or other VS Code fork silently install and run their code. This vulnerability is not hypothetical and has been exploited in the past, with the researchers finding 126 exact-ID hijacks, including names with millions of installs, where a developer typing the exact trusted identifier can still be handed code that is not the original.
- ▪The vulnerability is due to a dependency confusion problem in the OpenVSX registry, which is separate from Microsoft's Marketplace trust root.
- ▪An attacker can register an abandoned or never claimed publisher extension namespace on OpenVSX and have every Cursor, Windsurf, or other VS Code fork silently install and run their code.
- ▪The researchers found 126 exact-ID hijacks, including names with millions of installs, where a developer typing the exact trusted identifier can still be handed code that is not the original.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Medium |
| Canonical URL | https://medium.com/trendyol-tech/when-your-ide-becomes-a-rce-endpoint-c87b85096b19 |
| Publication time | Tue, 30 Jun 2026 07:47:04 +0000 |
| Retrieval time | 2026-06-30T07:54:24.163Z |
| Last seen | 2026-06-30T07:54:24.163Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | GCPezQ9UDink |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
When Your IDE Becomes a RCE EndpointBerk ALBAYRAK21 min read·1 hour ago--ListenSharePress enter or click to view image in full sizeTrendyol CSOC and Application Security research on a live supply-chain technique abusing Cursor and other VS Code-derived editors through the OpenVSX registry.TOCHow we found ourselves looking at thisMeasuring the blast radiusHow Cursor decides what to installWhat changed in June 2025Walking through an attack, step by stepIndicators you can trackHunting for itWhat you should do this weekWhere this goes nextIf your developers run Cursor, VSCodium, Windsurf, or any other fork of VS Code that pulls its extensions from OpenVSX, attacker controlled code is one editor launch away from executing on their machines.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.
Discussion
0 commentsMore from Medium
