Cursor, VS Code 1-click RCE

- AISLE said on July 31 it disclosed a one-click remote-code-execution flaw affecting Cursor, Microsoft VS Code and Google Antigravity. - AISLE said a malicious link embedded in a Git commit message could execute code with full terminal privileges and no warning. - Microsoft’s current VS Code release is version 1.132, dated August 5, 2026; AISLE said patched versions are now available.

AISLE said on July 31 that it had disclosed a one-click remote-code-execution flaw in Cursor, Microsoft Visual Studio Code and Google Antigravity, three editors built on or derived from the VS Code codebase. The company said the bug let an attacker hide malicious commands inside a link in a Git commit message and trigger code execution when a developer clicked it inside the editor. AISLE said the code ran with the victim’s terminal privileges and produced no warning prompt. The company said all three vendors have now patched the issue. ### How did a commit message become a code-execution path? AISLE said the exploit chain started with a malicious link embedded in a commit message that looked routine inside the editor’s source-control view. According to AISLE, clicking that link caused the editor to execute arbitrary code without a confirmation dialog or visible sign that anything had happened. (aisle.com) Cyber Security News and Cyber Press, citing AISLE’s findings, said the attacker would then inherit the same access level the developer had on the local machine. AISLE said that could include reading files, deleting data, installing persistent malware and extracting locally available credentials such as API keys. (aisle.com) ### Which products were affected, and why those three? AISLE said it first found the flaw in VS Code during automated scans of developer tooling in fall 2025. The company said Cursor inherited the same weakness because it is built on top of the VS Code codebase. AISLE said the issue later appeared in Google Antigravity in early 2026. (cybersecuritynews.com) The common thread was code reuse. AISLE said the same underlying bug moved across multiple editors that share VS Code architecture, turning one defect into a cross-product exposure. That account was repeated in follow-up reports published on August 5. ### Why are headlines talking about 50 million developers? (aisle.com) AISLE’s July 31 post said the affected tools are trusted by 50 million software engineers. Cyber Security News repeated that figure on August 5 in describing the size of the exposed user base across the three editors. Neither source published an independent user-by-user breakdown in the material reviewed here, but both used the number to describe the scale of the potential exposure. (cybersecuritynews.com) The number matters because these editors sit on developer workstations that often hold cloud credentials, repository access and local copies of production code. AISLE’s examples included OpenAI, Anthropic and Stripe API keys as data that could be taken from a compromised machine. ### Did vendors patch it, and what should users check now? (aisle.com) AISLE said Google and Cursor fixed the issue after disclosure and that Microsoft remediated VS Code later. The company said the bug is no longer present in current versions of Cursor, VS Code or Antigravity. Microsoft’s latest stable VS Code release is version 1.132, dated August 5, 2026, according to the company’s release-notes page. (aisle.com) AISLE said users should update to the latest version to avoid the flaw. Cyber Press also said security teams should review commit histories for suspicious links and rotate credentials if exposed machines may have used vulnerable versions. ### Why does this land differently from a normal desktop-software bug? AISLE’s description centered on the developer machine, not a consumer endpoint. The exploit path ran through a normal engineering workflow — reading source-control metadata inside a code editor — and the resulting access matched the developer’s own privileges on the workstation. (code.visualstudio.com) That makes the next steps operational rather than theoretical. Teams using Cursor, VS Code or Antigravity need to verify editor versions, inspect recent commit messages containing external links, and rotate secrets that may have been present on affected machines before patching. Microsoft’s current release page and AISLE’s disclosure are the two clearest places to confirm patch status and the original attack description. (aisle.com) (code.visualstudio.com)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.