Researchers at AISLE have disclosed a critical remote code execution vulnerability that affected the popular AI code editors Cursor, Microsoft Visual Studio Code and Google Antigravity. The flaw enabled an attacker to execute arbitrary code on a developer’s machine simply by embedding a malicious link inside a Git commit message. Approximately 50 million users were potentially at risk before patches were issued by all three vendors.
How the attack worked
The exploitation scenario closely mirrored normal development workflows. An attacker only needed to place a crafted link in a commit message. When a developer viewed the commit history inside the IDE and clicked the link, arbitrary code executed with the privileges of the current user. No pop-ups, confirmation dialogs or other indicators appeared during execution.
Successful exploitation allowed an attacker to:
- Steal API keys for services such as OpenAI, Anthropic and Stripe
- Install persistent malware that survived editor restarts
- Read or delete files on the local filesystem
- Run any commands under the logged-in user account
Why multiple editors were affected
Cursor was built as a fork of Visual Studio Code and inherited its architecture. The same underlying issue was later found in Google Antigravity, which also relies on VS Code components. This demonstrates the “shared component vulnerability” effect: when many AI tools reuse the same foundation, a single architectural flaw can propagate across multiple widely used products.
Why developers are high-value targets
Developer workstations typically contain corporate Git repositories, API and SSH keys, Kubernetes credentials and environment secrets. Compromising one machine often provides an initial foothold into broader corporate infrastructure. AI editors increase this risk by concentrating even more sensitive data and automation capabilities in a single environment.
Practical recommendations
Organizations using the affected editors should:
- Update to the latest patched versions immediately
- Scan developer workstations for suspicious activity
- Rotate any API keys, tokens or credentials that may have been stored locally
- Treat repository contents, including commit messages, as potentially untrusted
- Review AI-generated code and actions with heightened scrutiny
