A critical vulnerability in the Cursor code editor allows unauthenticated attackers to achieve remote code execution by tricking users into running the CLI within a malicious project directory.

The application suffers from the inclusion of functionality from an untrusted control sphere, where automatic loading of configuration files from the current working directory overrides global settings. This enables remote code execution through the manipulation of project-specific CLI configurations and prompt injection.

Successful exploitation of this vulnerability grants an attacker the ability to execute arbitrary code with the privileges of the user running the Cursor CLI. Given the CVSS score of 8.8, this presents a significant risk of full system compromise, data exfiltration, and lateral movement within the developer's environment. The potential for reputational damage and the loss of intellectual property through compromised source code repositories is substantial.

Immediate Action: Apply the vendor-provided patch version 2025.09.17-25b418f immediately to remediate the unsafe configuration loading mechanism.

Proactive Monitoring: Review developer workstation access logs and monitor for unexpected CLI execution patterns or unauthorized modifications to local .cursor/ directory contents.

Compensating Controls: Advise developers to avoid running Cursor CLI commands in untrusted or unknown project directories until the patch has been applied to their environment.

Public Exploit Available: No (exploit_available: false)

The severity of this remote code execution vulnerability necessitates immediate action, particularly for organizations that handle sensitive source code. Developers must prioritize the application of the specified patch version to ensure that project-specific configurations cannot be used to hijack the Cursor CLI environment. Failure to remediate this flaw leaves development workstations exposed to potential compromise by malicious repository content.