# CVE-2026-63093: Cursor for Windows 3.2.16 RCE via Malicious git.exe in Workspace

> Attackers can execute arbitrary code by placing a malicious git.exe in a repository, which Cursor automatically runs upon opening the project.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-prfr-jc65-hr23

## What is CVE-2026-63093?

CVE-2026-63093 is a high-severity code injection vulnerability in Anysphere, Inc. Cursor, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2026-63093?

It affects 1 product.


Products: Anysphere Cursor.

## How do I fix CVE-2026-63093?

No fix has been published for CVE-2026-63093 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63093 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63093 exists.

## Other vulnerabilities in Anysphere, Inc. Cursor

- [CVE-2026-50548](https://insights.sbomify.com/CVE-2026-50548/): Cursor Desktop sandbox escape via agent-controlled working directory (critical 9.3)
- [CVE-2026-50549](https://insights.sbomify.com/CVE-2026-50549/): Cursor Desktop sandbox escape via symlink and failed path canonicalization (critical 9.3)
- [CVE-2025-64106](https://insights.sbomify.com/CVE-2025-64106/): Cursor: Speedbump Modal Bypass in MCP Server Deep-Link (high 8.8)
- [CVE-2025-64107](https://insights.sbomify.com/CVE-2025-64107/): Cursor is Vulnerable to Path Manipulation Using Backslashes on Windows (high 8.8)
- [CVE-2025-64108](https://insights.sbomify.com/CVE-2025-64108/): Cursor's Sensitive File Modification can Lead to NTFS Path Quirks (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63093 and fix it if it is affected.

What it is: CVE-2026-63093 is a high-severity code injection vulnerability in Anysphere, Inc. Cursor, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63093 exists.

Affected product: Anysphere, Inc. Cursor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63093/ (Markdown: https://insights.sbomify.com/CVE-2026-63093/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63093
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63093
- OSV: https://osv.dev/vulnerability/CVE-2026-63093

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63093/
Summaries are generated and may contain mistakes; the official description above is the record.