News for hackers. Stuff that matters.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by beart on Tuesday July 14, 2026 @05:38PM (#48913245)
This doesn't require anyone placing anything deliberately on your machine (as in, needing to exploit it somehow ahead of time). It could be as simple as checking out a branch to review, where the author of the branch has added the .exe.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by Xirdus on Tuesday July 14, 2026 @06:29PM (#48913753)
I'd say checking out a malicious branch is in the same category as downloading a malicious attachment. By which I mean, it's kinda on you.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by krater23 on Tuesday July 14, 2026 @06:48PM (#48913917)
Downloading this attachement doesn't executes it. Checking out a branch in this case executes the file in the branch. Thats a big difference.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by dev_daftly on Tuesday July 14, 2026 @10:40PM (#48915612)
In this case, if you just run a git command yourself it executes the file as well.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by brookst on Wednesday July 15, 2026 @12:35AM (#48916339)
On windows I guess?

On Linux and MacOS you'd need to run ./git to execute a malicious binary in the cloned repo.

Re:Cursor 0day: When Full Disclosure Becomes the Only Protec... by beart on Tuesday July 14, 2026 @08:30PM (#48914752)
Okay... but when "you" is a junior engineer on your team and now you are suddenly spending your entire weekend dealing with malware, it's kinda on you as well.