Cursor 0day: When Full Disclosure Becomes the Only Protection Left

Post by dclowd9901 » Thu, Jul 16, 2026, 3:21 PM UTC

hack1312 wrote: post #218

dclowd9901 wrote: post #31

This draws to mind the dialog that opens when you open a new project in Cursor (and VSCode too, I think), where the IDE asks the user if they trust the project they're opening. Is Cursor under the impression that this is sufficient security apparatus?

Cursor, being based on VSCode, does have the Workspace Trust feature. They ship it disabled. https://cursor.com/docs/agent/security#workspace-trust

Ah, guess I was conflating the two (they are quite similar after all). From their documentation (the link you posted):

> For untrusted repos, use a basic text editor instead.

Is that really our options here? How shitty.

Post by cute_boi » Fri, Jul 17, 2026, 6:26 PM UTC

hnfong wrote: post #211

cute_boi wrote: post #136

Earlier quoted context omitted.

I agree cursor can fix the issue, but the main issue is downloading anything from untrusted source. The repo may have AGENTS.md which can tell please install npm package from random repo and run pnpm start etc... We should never ever download any pdf or excel macros etc.. from untrusted source.

If we take your logic to the extreme, then there are never any legitimate code execution vulnerabilities in web browsers since the user is not supposed to visit untrusted websites.

Correct, we shouldn't visit untrusted website unless it is from trusted source like banks etc.. There is reason why scamming is billion dollar industry.

Re: Cursor 0day: When Full Disclosure Becomes the Only Protection Left

Re: Cursor 0day: When Full Disclosure Becomes the Only Protection Left