Reported by 2 outlets

Timeline

1. update from gbhackers.com

   Cursor 0-Day Lets Attackers Execute Malicious Code by Opening a Repository

   gbhackers.com · 55d ago · August 19th, 2026

   A recently disclosed security issue in Cursor IDE exposed a serious Windows binary-planting vulnerability that could allow malicious code to execute simply by opening an untrusted repository. This flaw, tracked as CVE-2026-63093, relates to Cursor’s executable resolution behavior and demonstrates how files controlled by attackers placed in a workspace could be executed with the current […] The post Cursor 0-Day Lets Attackers Execute Malicious Code by Opening a Repository appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform .

2. update from cyberpress.org

   Cursor 0-Day Allows Arbitrary Code Execution by Simply Opening a Repository

   cyberpress.org · 55d ago · August 19th, 2026

   A newly disclosed Cursor IDE vulnerability demonstrates how opening an untrusted repository on Windows could lead to arbitrary code execution without prompt injection, AI-agent interaction, or any additional user approval. While the original issue centered on malicious git.exe binaries, subsequent research found the attack surface extended to other executables, including hatch.exe , under specific project conditions. AI security firm Mindgard initially reported the Cursor binary-planting flaw in December 2025 and publicly disclosed technical details in July 2026. The issue, tracked as CVE-2026-63093, involved Cursor’s handling of Git discovery during project load. Cursor 0-Day Allows Arbitrary Code Execution Cursor performs Git-related commands such as git rev-parse --show-toplevel during workspace initialization. On affected Windows configurations, this lookup could resolve a git.exe placed in the repository root before reaching the legitimate system Git installation. As a result, an attacker could distribute a repository containing a malicious git.exe . When a victim opened that folder in Cursor, the IDE could execute the planted binary under the victim’s user privileges. CVE-2026-63093 (Source: screetsec) The attack did not require the victim to run a build task, click an approval dialog, or interact with an AI feature. Opening the workspace was sufficient. However, Maland indicates the behavior was broader than Git binary resolution.