A critical remote code execution vulnerability discovered in three of the world's most popular code editors exposed an estimated 50 million software developers to complete system compromise with nothing more than a single click on a malicious link. The flaw, which affected Cursor, Microsoft VS Code, and Google Antigravity, has since been patched across all three platforms, but its discovery reveals how quickly security flaws can spread through AI-native developer tools that share common underlying code.

How Did This Vulnerability Work?

The exploit was deceptively simple yet devastating. An attacker could embed a malicious link inside a Git commit message. When a developer clicked that link inside the editor, the application executed arbitrary code with full terminal privileges, without displaying any confirmation dialog, warning prompt, or visible indication that anything had happened. Victims had no way to detect the compromise in real time, giving attackers a completely covert entry point into a developer's machine.

Once triggered, the vulnerability handed attackers the same level of access a developer has on their own laptop. This meant they could perform several dangerous actions without detection:

• Credential Theft: Exfiltrate sensitive credentials such as OpenAI, Anthropic, and Stripe API keys directly from the local environment.
• Persistent Malware Installation: Install persistent malware including keyloggers that broadcast every keystroke to an external server.
• File System Access: Freely crawl or delete files across the local file system without restriction.

Because the malware persisted even after the editor was closed, a single careless click could result in long-term, undetected surveillance of a developer's entire workflow.

How Did This Flaw Spread Across Multiple Products?

The vulnerability's journey across three major platforms illustrates a growing pattern in the AI coding tool ecosystem. Security researchers at AISLE first identified the flaw in VS Code during automated vulnerability scanning in fall 2025. Because Cursor is built directly on top of the VS Code codebase, it inherited the same underlying weakness, making the two of the most popular AI-assisted coding environments simultaneously vulnerable.

The story did not end there. In early 2026, the same vulnerability resurfaced in Google Antigravity, Google's newly launched AI-assisted coding environment, which was also derived from the VS Code architecture. AISLE promptly reported the issue to Google, which reacted quickly and remediated it within days. Cursor also moved fast to patch the flaw, while Microsoft's fix for VS Code arrived somewhat later. As of now, none of the current versions of Cursor, VS Code, or Google Antigravity contain the vulnerability.

Steps to Protect Yourself After This Vulnerability

• Update Immediately: Developers using any of these three editors should update to the latest available versions to ensure they are protected against the flaw.
• Review Commit History: Given that this vulnerability could operate entirely without user awareness, teams should review recent commit history to identify any suspicious activity.
• Rotate Credentials: Rotate any API keys or credentials that may have been exposed in projects handled through affected editor versions during the vulnerable period.

This case illustrates a critical vulnerability in how modern AI-native development tools are built. Because many AI-assisted IDEs are forked from a common codebase like VS Code, a single vulnerability can silently ripple across multiple products used by tens of millions of developers before it is caught. The speed and convenience that make these tools attractive for AI-assisted development are the same properties that accelerate the spread of security flaws.

The discovery underscores the value of continuous, AI-driven vulnerability detection to catch issues that traditional pattern-matching security tools might miss. As developers increasingly rely on AI-powered coding environments, the security implications of shared codebases become more urgent. A single flaw in a foundational technology can instantly compromise millions of developers worldwide, making rapid detection and patching essential for protecting the software supply chain.