Developer Tools Are Now Prime Targets, Not Side Utilities
The latest critical vulnerabilities in JetBrains TeamCity and the Cursor AI coding environment show that developer tools have become high-value attack surfaces where unauthenticated code execution can directly threaten CI/CD infrastructure, developer workstations, and downstream production systems. The idea that build servers and coding assistants are secondary security concerns is outdated; they are now central points of compromise that can expose configurations, credentials, and software supply chains in a single exploit. Treating these platforms as untrusted until patched is no longer extreme caution but the minimum responsible stance for any organization relying on automated builds and AI-assisted coding. TeamCity’s unauthenticated RCE vulnerability (CVE-2026-63077, CVSS 9.8) affects all TeamCity On-Premises versions and allows attackers with HTTP(S) access to execute operating system commands using the server’s privileges. Cursor’s Git vulnerability (CVE-2026-63093, CVSS 8.8) lets malicious repositories run attacker-controlled binaries on Windows developer machines when opened in affected versions. Taken together, these flaws underline a simple reality: attackers no longer need to fight for access to production; they can walk in through the tools developers rely on every day.
TeamCity RCE: When Your CI Server Becomes a Production Attack Bridge
The TeamCity RCE vulnerability is not a theoretical bug; it is a direct path from internet-facing CI servers to the heart of your environment. CVE-2026-63077 impacts every TeamCity On-Premises instance and allows an unauthenticated attacker to bypass normal checks via the agent polling protocol and execute arbitrary OS commands with the TeamCity server’s privileges. On a modern CI server, those privileges typically include access to build configurations, stored credentials, deployment scripts, and often direct connectivity to production databases and application stacks. According to JetBrains, “a successful attack could expose TeamCity data, configurations, and stored credentials, modify server state, and potentially compromise the integrity of build artifacts and downstream CI/CD pipelines”. This is a CI/CD security risk in the purest sense: compromise the orchestrator and you control every pipeline it runs. Given that state-sponsored groups and ransomware affiliates have targeted unpatched TeamCity servers before, leaving this TeamCity RCE vulnerability unpatched amounts to granting attackers a remote deployment console. JetBrains has shipped fixes in TeamCity On-Premises versions 2025.11.7 and 2026.1.3, and TeamCity Cloud has already been updated. There is also a security patch plugin for versions 2017.1 and later for admins who cannot upgrade immediately. The absence of known in-the-wild exploitation so far is not reassuring; it is a narrow window before proof-of-concept code makes scanning and compromise trivial.
Cursor Git Vulnerability: Malicious Repositories as a One-Click Developer Compromise
If TeamCity demonstrates how fragile CI servers are, Cursor’s Git vulnerability shows how easily attackers can turn everyday developer workflows into exploit chains. In affected Cursor for Windows version 3.2.16, simply opening a Git repository containing a malicious git.exe in its root directory was enough to give attackers code execution with the logged-in user’s privileges. The editor executed the repository’s git.exe instead of validating and using a trusted Git installation, meaning a cloned project could behave like a trojan application. Mindgard discovered the flaw last year and privately disclosed it to Cursor on December 14, with confirmation via the company’s bug bounty program in January. Yet the issue remained unpatched for roughly seven months and was only quietly fixed on July 13, one day before public disclosure. That delay is more than a process glitch; it signals that critical issues in AI coding tools may not be treated with the urgency they deserve. CVE-2026-63093 now carries a CVSS score of 8.8, reflecting the high severity of allowing arbitrary binaries from repositories to run on developer machines. Those machines usually contain proprietary source code, credentials, and secrets, making this Cursor Git vulnerability a potential starting point for software supply chain attacks that propagate from a single compromised workstation into customer-facing releases.
What Admins and Teams Must Do Now: Patch First, Re-Think Access Second
The responsible response to these unauthenticated RCE exploits is immediate, practical, and non-negotiable. For TeamCity, admins of On-Premises servers should upgrade to versions 2025.11.7 or 2026.1.3, or install the JetBrains security patch plugin if they are still running 2017.1 or later. Older instances between 2017.1 and 2018.1 must be restarted after plugin installation, while later versions can enable the plugin without a restart. Relying on the absence of currently known exploitation attempts is reckless when scanning for CI servers has already been part of attacker playbooks. Beyond patching, organizations should stop treating CI servers as public-facing appliances. JetBrains itself recommends limiting network access to TeamCity to trusted networks, or enforcing VPN and extra security layers for internet-facing servers. Even exposing a login screen or REST API widens the attack surface for future flaws. For Cursor, teams must ensure Windows installations are updated beyond version 3.2.16 and should review policies around cloning and opening untrusted repositories. Developers should assume that any tool which automatically discovers and runs binaries during initialization can be co-opted by malicious projects. Security teams need to incorporate developer tooling—CI/CD platforms, IDEs, and AI assistants—into their regular patch cycles and threat modeling. If your build server or editor can execute code, it must be treated with the same rigor as production workloads.
