Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by dclowd9901 on Tuesday July 14, 2026 @05:16PM
(#48913055)
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?
[ Parent
| on HN ]
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by shitter on Tuesday July 14, 2026 @05:44PM
(#48913305)
Since there are no approval dialogs, it sounds like that doesn't even come into play here. That is the "gate" (to use the AI parlance) that Microsoft places on code execution in workspaces, though, and I would expect Cursor to at minimum fix this to only execute git.exe in trusted workspaces.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by alansaber on Tuesday July 14, 2026 @05:51PM
(#48913382)
Startups historically are not the most security oriented
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by hack1312 on Wednesday July 15, 2026 @11:14AM
(#48922113)
Cursor, being based on VSCode, does have the Workspace Trust feature.
They ship it disabled.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by dclowd9901 on Thursday July 16, 2026 @11:21AM
(#48935802)
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.