Which versions of Cursor IDE are affected by CVE-2026-63093?

Cursor for Windows 3.2.16 contains a critical vulnerability enabling arbitrary code execution on developer workstations whenever a crafted repository is cloned and opened, directly exposing…

Is there a public PoC exploit available for CVE-2026-63093?

Yes, a public proof-of-concept exploit is available for CVE-2026-63093. Prioritise patching immediately. EPSS: 0.4%.

How to fix or mitigate CVE-2026-63093?

Within 24 hours, inventory all Cursor 3.2.16 installations on Windows systems and immediately either uninstall the application or restrict developer access exclusively to internal, controlled repositories until a vendor patch is available. Within 7 days, deploy repository scanning mechanisms to detect and quarantine any executable files matching malicious git.exe signatures before developers pull them, and implement process monitoring on development workstations to alert on unexpected child processes spawned by git.exe. Within 30 days, establish continuous monitoring for Cursor security advisories and release notes; prepare a rapid-deployment procedure to update all instances to patched versions within 24 hours of availability, and evaluate migration to alternative development tools if patching is significantly delayed.

Cursor IDE CVE-2026-63093

Q: What is the CVSS score of CVE-2026-63093?

CVE-2026-63093 has a CVSS 4.0 base score of 8.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.4%.

EUVD-2026-45178 HIGH

Untrusted Search Path (CWE-426)

2026-07-17 VulnCheck

GHSA-prfr-jc65-hr23

RCE Microsoft Cursor

8.7

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

8.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.8 HIGH

Malicious repo is network-delivered (AV:N, AC:L, PR:N) but the victim must open the workspace (UI:R); code runs as current user with full C/I/A impact and no scope change (S:U).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Analysis Generated

Jul 17, 2026 - 15:16 vuln.today

CVE Published

Jul 17, 2026 - 14:23 cve.org

HIGH 8.7

DescriptionCVE.org

Cursor for Windows version 3.2.16 contains a binary planting vulnerability that allows remote attackers to achieve arbitrary code execution by placing a malicious git.exe file in the repository root directory. When a developer clones and opens a crafted repository, Cursor automatically resolves and executes the workspace-resident git.exe during IDE startup and on a recurring timed cadence without any user interaction, running the malicious binary under the privileges of the current user.

AnalysisAI

Arbitrary code execution in Cursor for Windows 3.2.16 lets remote attackers run code on a developer's machine by planting a malicious git.exe in a repository's root directory. Because Cursor resolves and executes the workspace-resident git.exe at IDE startup and on a recurring timer, simply cloning and opening a crafted repository triggers execution under the current user's privileges with no explicit user action beyond opening the project. Publicly available exploit code exists and the flaw was reported by VulnCheck; there is no CISA KEV listing or active-exploitation confirmation in the data.

Technical ContextAI

The affected product is Anysphere's Cursor, an AI-assisted code editor forked from VS Code (CPE cpe:2.3:a:anysphere,_inc.:cursor). The root cause is CWE-426 (Untrusted Search Path / binary planting): rather than invoking git.exe from a trusted absolute system path, Cursor resolves the executable relative to the opened workspace, so an attacker-controlled git.exe placed in the repository root is preferred and launched. On Windows, executable resolution that includes the current working directory or relative paths is a classic search-order hijack vector, and IDEs routinely shell out to git for status polling, branch info, and other repository operations - here that behavior fires both at startup and on a recurring timed cadence, giving repeated execution opportunities.

RemediationAI

No vendor-released patch identified at time of analysis; no fixed version is present in the provided data, and the Mindgard disclosure title suggests remediation was not yet coordinated. As specific compensating controls: avoid opening or cloning untrusted repositories in Cursor on Windows, and inspect a repository's root for an unexpected git.exe (or other planted binaries) before opening it - the trade-off is added manual review friction. Configure Cursor/Git to use an absolute, trusted git path (for example, point the git executable setting to the system Git installation such as C:\Program Files\Git\cmd\git.exe) so workspace-relative resolution is bypassed, and verify this actually overrides Cursor's resolution logic since the flaw is in how Cursor locates the binary. Consider running Cursor as a least-privileged user and monitoring for git.exe launched from user project directories. Consult the VulnCheck advisory (https://www.vulncheck.com/advisories/cursor-for-windows-rce-via-malicious-git-exe-in-workspace) and vendor site (https://cursor.com/) for an official fixed release before relying solely on workarounds.