CVE-2026-63093: Cursor for Windows RCE Vulnerability

CVE-2026-63093 Overview

CVE-2026-63093 is a binary planting vulnerability in Cursor for Windows version 3.2.16. The flaw allows remote attackers to achieve arbitrary code execution by placing a malicious git.exe file in a repository root directory. When a developer clones and opens a crafted repository, Cursor automatically resolves and executes the workspace-resident git.exe during Integrated Development Environment (IDE) startup and on a recurring timed cadence. The execution occurs without any user interaction beyond opening the workspace, running the malicious binary under the privileges of the current user. The vulnerability is classified under CWE-426: Untrusted Search Path.

Critical Impact
Attackers can achieve arbitrary code execution on a developer workstation simply by convincing the user to open a malicious repository in Cursor, with no additional prompts or clicks.

Affected Products

Cursor for Windows version 3.2.16
Windows developer workstations running the affected Cursor IDE build
Downstream code repositories opened within the vulnerable IDE

Discovery Timeline

2026-07-17 - CVE-2026-63093 published to the National Vulnerability Database (NVD)
2026-07-17 - Last updated in NVD database

Technical Details for CVE-2026-63093

Vulnerability Analysis

Cursor for Windows relies on git.exe to perform source control operations inside opened workspaces. The IDE resolves the git.exe binary using an untrusted search path that includes the workspace root before trusted system locations. An attacker who controls the contents of a repository can drop a malicious git.exe at the repository root. Cursor then executes that binary automatically on startup and repeatedly on a timed schedule. The impact spans confidentiality, integrity, and availability because the attacker-supplied code runs in the security context of the interactive user. Because developer workstations frequently hold source code, cloud credentials, and signing keys, successful exploitation provides a foothold into wider software supply chains.

Root Cause

The root cause is improper resolution of the git.exe executable path. Cursor searches the workspace directory before validated system directories such as %ProgramFiles%\Git\bin. This behavior maps to CWE-426: Untrusted Search Path. The IDE does not validate the origin, signature, or location of the resolved binary before invoking it.

Attack Vector

The attack requires the target developer to open an attacker-controlled repository in Cursor. The attacker publishes a repository containing a malicious git.exe at the project root. When the victim clones and opens the workspace, Cursor invokes the planted binary during IDE initialization. The IDE then re-invokes git.exe on its recurring polling interval, giving the payload multiple execution opportunities. Additional technical detail is available in the Mindgard 0-Day Blog Post and the VulnCheck RCE Advisory.

No verified proof-of-concept code is published in the referenced advisories, so exploitation is described in prose only. The core primitive is placement of a Windows Portable Executable named git.exe at the repository root, which Cursor then launches with the current user's token.

Detection Methods for CVE-2026-63093

Indicators of Compromise

Presence of a git.exe file at the root of any cloned repository or workspace directory.
Process creation events where Cursor.exe spawns a git.exe located in a user-writable path such as C:\Users\<user>\source\<repo>\git.exe.
Outbound network connections initiated by a git.exe process running from a workspace directory rather than a Git installation directory.

Detection Strategies

Alert on execution of any git.exe whose parent path is not an approved Git installation directory such as C:\Program Files\Git\ or C:\Program Files (x86)\Git\.
Flag Cursor.exe parent-child process trees that invoke unsigned or non-Microsoft, non-Git-signed executables.
Hunt for repositories in developer home directories that contain executable files with names matching common developer tools (git.exe, node.exe, python.exe) at the repository root.

Monitoring Recommendations

Enable command-line and process-creation logging on developer workstations, including Windows Event ID 4688 and Sysmon Event ID 1.
Forward endpoint telemetry to a centralized data lake or Security Information and Event Management (SIEM) platform for cross-workstation correlation.
Baseline the legitimate git.exe install path for each host and alert on deviations from that baseline.

How to Mitigate CVE-2026-63093

Immediate Actions Required

Instruct developers to avoid opening untrusted repositories in Cursor for Windows 3.2.16 until a vendor patch is available.
Scan existing workspace directories for any git.exe file at the repository root and quarantine matches.
Restrict execution of binaries from user-writable paths using Windows Defender Application Control or AppLocker policies.

Patch Information

At the time of NVD publication on 2026-07-17, no fixed version is listed in the CVE record. Monitor the Cursor Official Site and the VulnCheck RCE Advisory for patch availability and upgrade guidance.

Workarounds

Configure Cursor to use an absolute path to the trusted system git.exe if the setting is exposed, preventing workspace-relative resolution.
Remove the current directory and workspace directory from any inherited PATH used by the IDE process.
Open unknown repositories inside an isolated virtual machine or Windows Sandbox that has no access to credentials or corporate resources.
Apply application allowlisting to block execution of any .exe file located under developer source directories.

bash

# Configuration example: AppLocker rule concept to block executables from user source directories
# Deny execution of any .exe under C:\Users\*\source\* and common repo locations
New-AppLockerPolicy -RuleType Path `
  -User Everyone `
  -Action Deny `
  -Path "C:\Users\*\source\*\*.exe"