As cited
Copy frozen at (site build).
vulnerabilities
Cursor Flaw Lets Malicious Cloned Repositories Trigger Windows Code Execution
Cursor on Windows automatically executes a binary named git.exe in the root of any opened repository without user interaction, approval, or warnings. An attacker can exploit this by cloning a malicious repository containing git.exe to gain arbitrary code execution with the developer's credentials and access to source code, SSH keys, and cloud tokens. The executable runs repeatedly while the project remains open.
Why it matters: Developers using Cursor on Windows face code execution risk when opening untrusted or cloned repositories, potentially exposing credentials and tokens; patching or disabling auto-execution of binaries in project roots is urgent.
- Source published
- First seen by Cybersecurity Tracker
Source attribution
Correction
Correction recorded as of .
vulnerabilities
Cursor Flaw Lets Malicious Cloned Repositories Trigger Windows Code Execution
Cursor on Windows automatically executes a binary named git.exe in the root of any opened repository without user interaction, approval, or warnings. An attacker can exploit this by cloning a malicious repository containing git.exe to gain arbitrary code execution with the developer's credentials and access to source code, SSH keys, and cloud tokens. The executable runs repeatedly while the project remains open.
Why it matters: Developers using Cursor on Windows face code execution risk when opening untrusted or cloned repositories, potentially exposing credentials and tokens; patching or disabling auto-execution of binaries in project roots is urgent.
- Source published
- First seen by Cybersecurity Tracker