Cursor IDE EUVD-2026-45178

Exploitation requires the victim to clone and open, in Cursor for Windows 3.2.16, a repository that contains an attacker-supplied git.exe in the repository root directory; the vulnerable behavior is Cursor automatically resolving the workspace-resident git.exe during IDE startup and on a recurring timed cadence. The exploitation-enabling condition is Cursor's relative/workspace-based resolution of the git executable, and the required trigger is opening the crafted workspace (UI:P - passive interaction, no action beyond opening the project). Limiting factors: the target must be on the Windows build, must be running the affected Cursor version, and must be induced to open the malicious repository; code runs only at the current user's privilege level (no privilege escalation is claimed). No prior authentication to the victim system is needed (PR:N).

The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H, base 8.7) reflects network-delivered content, low complexity, no privileges, and passive user interaction, with high impact to confidentiality, integrity, and availability but no scope change to other systems. PR:N indicates unauthenticated triggering - the attacker needs no account on the victim's machine, only to get the victim to clone and open a repository. UI:P (passive) combined with automatic timed re-execution meaningfully lowers the real-world barrier versus a flaw needing deliberate victim action. Publicly available exploit code raises practical risk, but there is no CISA KEV entry and no EPSS score provided, so widespread active exploitation is not confirmed - treat this as a high-priority, POC-backed developer-workstation threat rather than a confirmed in-the-wild campaign. The chief limiting factor is social: the victim must be convinced to open a malicious repository.

An attacker publishes an attractive-looking repository (a sample project, coding challenge, or dependency) containing a malicious git.exe in its root and lures a developer into cloning and opening it in Cursor for Windows. On IDE startup - and again on the recurring timer - Cursor resolves and executes the planted git.exe with the developer's privileges, giving the attacker code execution with no further interaction. Publicly available exploit code lowers the effort required to reproduce this.