Loading vulnerability…
Binary Planting RCE in Cursor for Windows 3.2.16
CVE-2026-63093 is a remote code execution vulnerability in Anysphere Cursor for Windows version 3.2.16 caused by unsafe executable resolution during repository handling. When Cursor opens a crafted repository, it performs Git-related operations and resolves a Git executable in a way that permits a workspace-resident binary to be selected and launched. An attacker can place a malicious git.exe in the repository root, and Cursor will automatically execute it during IDE startup and on a recurring timed cadence without additional user interaction. The flaw is a binary planting issue in which the application fails to ensure that only a trusted Git installation is invoked, allowing attacker-controlled code from the opened workspace to run under the current user context.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation results in arbitrary code execution on the developer workstation with the privileges of the logged-in user. This can enable theft of source code, credentials, tokens, and deployment secrets; modification of local projects; installation of persistence; and use of the compromised development environment as a staging point for broader software supply chain compromise.
If you can’t patch tonight, do this now.
Until patched versions are fully deployed, avoid opening untrusted or newly cloned repositories in vulnerable Cursor for Windows installations. Review repositories for unexpected executable files in the project root and remove malicious binaries before opening them. Restrict developer workflows to trusted repositories, use endpoint controls to detect execution of unexpected workspace-resident binaries, and scan developer systems and repositories for suspicious planted executables.
Patch, then assume compromise.
Update Cursor for Windows to a version that addresses the unsafe binary resolution behavior. The fix should ensure Cursor invokes Git only from trusted, explicitly validated locations rather than searching the opened workspace for executables. Repositories should also be inspected for unauthorized executable files that could have been planted to trigger this behavior.
No public exploits tracked yet. Mallory keeps watching.
10 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.