SECURITYHIGHCVE-2026-63093

CVE-2026-63093: Cursor for Windows Binary Planting Allows RCE via Malicious Git Repository

A high-severity binary planting vulnerability in Cursor for Windows 3.2.16 enables remote attackers to achieve arbitrary code execution by placing a rogue...

Dylan H.

Security Team

July 18, 2026
3 min read
CVE-2026-63093: Cursor for Windows Binary Planting Allows RCE via Malicious Git Repository

Affected Products

  • Cursor for Windows 3.2.16

Overview

CVE-2026-63093 is a binary planting vulnerability discovered in Cursor for Windows version 3.2.16. The flaw allows a remote attacker to achieve arbitrary code execution on a victim's machine by embedding a malicious git.exe file in the root of a crafted repository.

When a developer clones and opens the repository in Cursor, the IDE automatically resolves git.exe from the repository root rather than from a trusted system path — silently executing attacker-controlled code with the privileges of the current user.

FieldDetail
CVE IDCVE-2026-63093
CVSS Score8.8 (High)
Affected SoftwareCursor for Windows 3.2.16
Attack VectorNetwork (social engineering / repository share)
Privileges RequiredNone
User InteractionRequired (clone + open repository)
Published2026-07-17

Technical Details

Binary planting (also known as DLL/EXE hijacking) occurs when an application resolves a dependency by searching relative or attacker-controlled paths before trusted system directories. In this case, Cursor's Git integration uses git.exe without enforcing an absolute, verified path — allowing the current working directory or repository root to shadow the legitimate binary.

Attack chain:

  1. Attacker crafts a repository containing a malicious git.exe at the root.
  2. Victim is social-engineered into cloning the repository (e.g., via a link, issue, or collaboration invite).
  3. Victim opens the cloned folder in Cursor for Windows.
  4. Cursor automatically invokes git.exe for version control operations.
  5. The malicious git.exe executes in the context of the victim's user account.

This attack requires no elevated privileges and no special Cursor permissions — only that the victim open the repository in the vulnerable IDE version.

Impact

A successful exploit grants the attacker arbitrary code execution on the developer's workstation with the privileges of the logged-in user. Given that developers typically have access to credentials, SSH keys, cloud tokens, and source code, the blast radius extends well beyond the local machine.

Potential downstream impacts include:

  • Credential and token theft (AWS, GitHub, Azure keys stored in environment or config files)
  • Lateral movement within corporate networks
  • Supply chain compromise if the developer has write access to CI/CD pipelines or package registries
  1. Update Cursor to a patched version above 3.2.16 as soon as one is available from the vendor.
  2. Audit open repositories — avoid opening untrusted or unreviewed repositories in Cursor until patched.
  3. Review PATH configuration — ensure system Git is installed in a trusted, non-user-writable location (C:\Program Files\Git\bin).
  4. Enable Windows Defender ASR rules targeting executable planting in user-writable directories.
  5. Monitor for unexpected git.exe processes originating outside Program Files.

References