A severe remote code execution (RCE) vulnerability has been identified in three widely used code editors: Cursor, Microsoft VS Code, and Google Antigravity. This flaw, discovered by AISLE, poses a significant risk to approximately 50 million developers, as it allows complete system compromise with just a single click on a malicious link.
Details of the RCE Vulnerability
The vulnerability exploits a straightforward yet dangerous method. Attackers can embed a harmful link within a Git commit message. When a developer clicks this link in their editor, the application runs arbitrary code without any warnings or confirmation prompts, granting attackers full terminal access.
This covert entry allows attackers to extract sensitive credentials, such as OpenAI and Stripe API keys, install persistent malware, and manipulate the local file system without detection. The malware remains even after the editor is closed, potentially leading to prolonged surveillance of a developer’s activities.
Discovery and Response
AISLE’s research team first detected the flaw in VS Code during an automated scan in fall 2025. Since Cursor shares the same codebase, it inherited the vulnerability. AISLE responsibly disclosed the issue to both Microsoft and Cursor, enabling them to address the problem.
The vulnerability later appeared in Google Antigravity, which is also based on the VS Code architecture. AISLE notified Google, which rapidly resolved the issue. Cursor and Google quickly patched their platforms, while Microsoft took a bit longer to issue a fix for VS Code. Currently, all three platforms have addressed the vulnerability.
Implications for Developers
This incident highlights a broader risk within AI-native development tools. As many IDEs are derived from common codebases like VS Code, a single vulnerability can propagate rapidly across multiple platforms. The convenience of these tools for AI-assisted development also accelerates the spread of such security flaws.
AISLE’s findings emphasize the need for continuous, AI-driven vulnerability detection to identify issues that may be overlooked by traditional security tools. Developers should update their editors to the latest versions and review their commit histories and credentials to ensure their systems remain secure.
In conclusion, developers using these tools must act promptly to safeguard their projects. It’s vital to rotate any exposed API keys and ensure all software is up-to-date to prevent potential breaches.
