Code execution via workspace-root Git binary planting
Published Jul 17, 2026 · Updated Jul 17, 2026
Binary planting in Anysphere Cursor 3.2.16 for Windows allows remote attackers to execute code through a crafted repository. Cursor's Git path resolver treats the repository root as a trusted binary location and repeatedly launches a workspace-resident git.exe. A developer must clone and open the repository, after which the binary runs without another prompt under the current user's privileges.
Summary
What happened
Binary planting in Anysphere Cursor 3.2.16 for Windows allows remote attackers to execute code through a crafted repository. Cursor's Git path resolver treats the repository root as a trusted binary location and repeatedly launches a workspace-resident git.exe. A developer must clone and open the repository, after which the binary runs without another prompt under the current user's privileges.
The record
- CVE
- CVE-2026-63093
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- Anysphere
- Product
- Cursor
- Classifications
- CWE-426, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.2.16
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Workspace-root git.exe Calculator proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo