2.2K
A critical security vulnerability in Cursor git.exe has been discovered, allowing a renamed file to take control of any Windows machine using the popular AI coding tool. Despite being reported seven months ago, a fix is still pending. AI security firm Mindgard released detailed technical information on July 14, 2026, after private disclosure failed to yield results.
![\"A](\"https://latesthackingnews.com/wp-content/uploads/2026/07/a-close-up-of-code-in-an-editor-on-a-laptop-screen-represent.jpg\")
The vulnerability lies in how Cursor resolves the Git binary when opening a project on Windows. The IDE searches various locations for git.exe, including the root of the workspace itself. By placing a file named git.exe in the top-level folder of a repository, an attacker can execute it without any user interaction.
Understanding the Vulnerability
Mindgard demonstrated the vulnerability by renaming the Windows Calculator app to git.exe and placing it in a test repository. When the folder was opened in Cursor, the fake binary was repeatedly launched, mimicking legitimate Git commands. This exploit can lead to unauthorized code execution and access to sensitive data.
This method of attack is concerning as it can be easily triggered by unsuspecting developers when cloning public repositories. It bypasses traditional security measures and poses a significant threat to the integrity of source code and credentials.
Lack of Response and Patch
Despite being reported to Cursor’s security team in December 2025, the vulnerability remains unpatched. Mindgard’s attempts to follow up were met with silence until they decided to publicly disclose the issue on July 14, 2026. Cursor has yet to acknowledge the flaw officially or assign a CVE ID.
Similar vulnerabilities were also found in other AI coding assistants, highlighting a broader trend of unsafe binary resolution behavior on Windows. While some vendors like AWS promptly addressed the issues, others including Cursor have been slow to respond.
Recommendations for Defense
Until a patch is released, users are advised to treat external repositories with caution and consider opening them in isolated environments. Organizations managing Windows developer environments should implement strict execution control measures to mitigate the risk posed by such vulnerabilities.
