News for hackers. Stuff that matters.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by melodyogonna on Wednesday July 15, 2026 @04:37AM (#48917924)
People are offloading a lot of responsibilities to tools. If you pull a repository from Github without doing due diligence then you can't blame Cursor for getting compromised
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by iainmerrick on Wednesday July 15, 2026 @08:30AM (#48919825)
What’s due diligence? Reading all the code on GitHub?

That’s not a great interface, you probably want to clone it and open in your IDE so you can inspect the code properly...

Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by hnfong on Wednesday July 15, 2026 @09:43AM (#48920733)
So I clone a repo from Github and try to do due diligence before compiling and executing the code. I open the project with my IDE/text editor, and boom, I get pwned while doing the due diligence.

Unless it's Cursor's stance that people should use Emacs or whatever to check the repo before opening it, this is "you're holding it wrong" level stupid gaslighting.