Cursor up to 1.7 /.cursor/cli.json inclusion of functionality from untrusted control sphere

Summaryinfo

A vulnerability labeled as critical has been found in Cursor up to 1.7. This issue affects some unknown processing of the file /.cursor/cli.json. Such manipulation leads to inclusion of functionality from untrusted control sphere. This vulnerability is traded as CVE-2025-61592. The attack may be launched remotely. There is no exploit available. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability was found in Cursor up to 1.7. It has been rated as critical. Affected by this issue is an unknown part of the file /.cursor/cli.json. The manipulation with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. Using CWE to declare the problem leads to CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Cursor is a code editor built for programming with AI. In versions 1.7 and below, automatic loading of project-specific CLI configuration from the current working directory (/.cursor/cli.json) could override certain global configurations in Cursor CLI. This allowed users running the CLI inside a malicious repository to be vulnerable to Remote Code Execution through a combination of permissive configuration (allowing shell commands) and prompt injection delivered via project-specific Rules (/.cursor/rules/rule.mdc) or other mechanisms. The fix for this issue is currently available as a patch 2025.09.17-25b418f. As of October 3, 2025 there is no release version.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-61592 since 09/26/2025. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.

By approaching the search of inurl:.cursor/cli.json it is possible to find vulnerable targets with Google Hacking.

Applying a patch is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-32311). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Cursor

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7

Website

• Product: https://github.com/cursor/cursor/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion