Anysphere Cursor 3.2.16 Git git.exe uncontrolled search path
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.76 |
Summary
A vulnerability classified as critical was found in Anysphere Cursor 3.2.16. Affected by this issue is some unknown functionality of the file git.exe of the component Git Handler. Such manipulation leads to uncontrolled search path. This vulnerability is referenced as CVE-2026-63093. The attack can only be performed from a local environment. No exploit is available.
Details
A vulnerability, which was classified as critical, has been found in Anysphere Cursor 3.2.16. Affected by this issue is an unknown function of the file git.exe of the component Git Handler. The manipulation with an unknown input leads to a uncontrolled search path vulnerability. Using CWE to declare the problem leads to CWE-427. The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at mindgard.ai. This vulnerability is handled as CVE-2026-63093 since 07/15/2026. The exploitation is known to be difficult. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/17/2026). The MITRE ATT&CK project declares the attack technique as T1574.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.0VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.0
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Uncontrolled search pathCWE: CWE-427 / CWE-426
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/15/2026 CVE reserved07/17/2026 Advisory disclosed
07/17/2026 VulDB entry created
07/17/2026 VulDB entry last update
Sources
Advisory: mindgard.aiStatus: Not defined
CVE: CVE-2026-63093 (🔒)
GCVE (CVE): GCVE-0-2026-63093
GCVE (VulDB): GCVE-100-379820
Entry
Created: 07/17/2026 17:04Changes: 07/17/2026 17:04 (53)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.