Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by gene91 on Tuesday July 14, 2026 @04:11PM
(#48912373)
Modern day code agents would clone a repo and read the code when you ask it a question about an API that’s not clearly documented. This vulnerability is real.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by paxys on Tuesday July 14, 2026 @07:34PM
(#48914333)
This is exactly why every AI agent should run in a sandbox.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by TZubiri on Wednesday July 15, 2026 @12:39AM
(#48916361)
Don't think that would trigger the bug, it needs to be at the repo root when the user opens the agent CLI, it's not like the agent is calling another agent CLI process with the new repo root as its project root.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by AntonyGarand on Tuesday July 14, 2026 @04:02PM
(#48912262)
The malicious payload can live on the remote: `git clone` a repo, open it with cursor, and you're compromised
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by 4ndrewl on Tuesday July 14, 2026 @06:09PM
(#48913545)
It's curious the number of people here who can't link these two things.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by dev_daftly on Tuesday July 14, 2026 @10:45PM
(#48915637)
git clone a repo, cd into the directory, git checkout ..., and you're compromised
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by pixl97 on Tuesday July 14, 2026 @04:06PM
(#48912312)
>You need to have an already malicious payload on your pc to make this exploit work
Uh, no, not exactly from what I'm reading.
At least from my piss poor understanding of it, you could possibly prompt inject something like "download https://github.com/hackmycursor/exploit.git". Would an agent do this, I'm unsure, but if so, it would download the git.exe and execute it.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by trollbridge on Tuesday July 14, 2026 @04:07PM
(#48912328)
This has been a problem with agent harnesses for as long as I've used them - prompting them to retrieve something often results in them going the extra mile and running and installing it.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by JMKH42 on Tuesday July 14, 2026 @04:02PM
(#48912263)
wouldn't the attack vector be like this:
I find a github repo, I want to contribute to it. I clone it, open up cursor, make an edit, commit, and boom, I am infected.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by Illniyar on Tuesday July 14, 2026 @04:51PM
(#48912788)
you would only need to open it to be exploited, not edit or prompt. Allegedly
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by dalemhurley on Tuesday July 14, 2026 @05:09PM
(#48912990)
From the article it occurs when Cursor is loaded. iDEs do a lot of stuff when they first open.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by skeledrew on Tuesday July 14, 2026 @04:55PM
(#48912830)
From my reading, boom happens at "open up cursor".
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by dev_daftly on Tuesday July 14, 2026 @07:52PM
(#48914477)
You can leave out cursor and it would do the same thing.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by dalemhurley on Tuesday July 14, 2026 @05:06PM
(#48912955)
If your an opensource developer you may get a pull request containing the the git.exe
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by ribs on Tuesday July 14, 2026 @05:24PM
(#48913129)
I think you’ve got it wrong; no malicious payload need be on your box already. That’s not what the article says.
Re:Cursor 0day: When Full Disclosure Becomes the Only Protec...
by ryanisnan on Tuesday July 14, 2026 @06:16PM
(#48913615)
Uh, I don't think people typically associate downloading a repository, and viewing the source, as being synonymous with activating a malicious payload. That is the bit that's concerning.
I'm also so tired of people groaning about AI writing, yes, it's annoying, but attack the message, not the messenger.
You need to have an already malicious payload on your pc to make this exploit work. I can understand the severity of the exploit but at the same time I’d hope to not have to run into this situation for it to happen in the first place