Introduction
JetBrains TeamCity sits at the center of many software delivery pipelines, with access to source code, build configurations and deployment processes. Any service running next to it that accepts commands without checking who sent them deserves a close look. In affected TeamCity releases, the helper process used for Team Foundation Server (TFS) integration exposed that kind of service, a command server that did not authenticate its callers.
JetBrains, acting as CNA, tracks the issue as CVE-2026-133089. It classifies the flaw as CWE-306 (Missing Authentication for Critical Function) and rates it CVSS 3.1 8.1 High. The fixes shipped in TeamCity 2026.2.2 and 2026.1.6, both published on 3 November 2026. Public technical detail is limited, so this post briefly summarizes what is documented and is explicit about what is not.
Technical information
Root cause
TeamCity integrates with Azure DevOps Server / TFS through a native Windows helper, tfs-native.exe. The helper ships inside the TFS plugin archive tfs-support.jar, under /bin/. At runtime, TeamCity copies it into its temp directory as TC-TFS-NATIVE-<digits>.exe.
The Java side of TeamCity drives this helper over a local command channel. In vulnerable builds that channel had no authentication, so anything that could reach the listener could send it commands. JetBrains' security bulletin entry for the issue (TW-104277) states it plainly: "The TFS helper process exposed an unauthenticated command server."
The assigned weakness, CWE-306, describes critical functionality that lacks authentication. MITRE's general guidance notes that the resulting privileges and consequences depend on what functionality is exposed. That general description is not evidence of any specific command or impact beyond what the CVE record states.
For context, JetBrains documentation describes TeamCity's Team Foundation Version Control integration as communicating with Azure DevOps repositories, including through personal access token connections. That documentation does not describe the vulnerable helper. It also does not establish that repository credentials are needed to exploit this CVE.
Reading the CVSS vector
The CNA vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. It is the most precise technical characterization currently public:
AV:N: the attack vector is network.AC:H: attack complexity is high, so exploitation should not be described as trivial or guaranteed.PR:NandUI:N: no privileges and no user interaction are required.S:UwithC:H/I:H/A:H: scope is unchanged, and confidentiality, integrity and availability impacts are each rated high.
One of several TFS helper fixes
The TFS helper received security fixes across two consecutive update cycles, and patch planning depends on that sequence:
- 2026.2.1 / 2026.1.5: CVE-2026-133057 fixed the TFS helper server being "exposed on all network interfaces" (CWE-1327, rated Low at 3.7). This narrowed who could reach the listener.
- 2026.2.2 / 2026.1.6: CVE-2026-133089 (TW-104277) addresses the separate problem that the listener did not authenticate its callers. In the same release, JetBrains also fixed TW-104134, an XXE in the TFS helper process, also rated High.
Fixing the binding limits how far the listener can be reached over the network, but anything that can still reach it can issue commands. Requiring authentication closes that remaining gap. This is why installations that took 2026.2.1 or 2026.1.5 for the earlier fix still need 2026.2.2 or 2026.1.6.
Attack flow, as far as it is documented
Based on the public record, an attack follows this general shape:
- Reach the listener. The attacker needs network reachability to the TFS helper's command server. Before 2026.2.1 / 2026.1.5, the listener was exposed on all network interfaces (CVE-2026-133057). On later builds, the set of hosts that can reach it is narrower.
- Issue commands without credentials. The command server performs no authentication, so the attacker can send commands without any TeamCity account or user interaction. This matches
PR:NandUI:N. - Effect depends on the command set. The CNA rates confidentiality, integrity and availability impact as high. The specific commands, and what they can do, are not public.
Several details remain undisclosed: the wire protocol, the listening port, the exact conditions for reaching the helper, and the commands it accepts. We are not aware of any published proof of concept.
What has not been disclosed
TeamCity's server is closed source. No commit, diff or standalone hotfix for TW-104277 is public, so the exact fix mechanism is unknown. A per-launch shared secret, a handshake, or restricting the transport to the parent process are all plausible approaches, but JetBrains has confirmed none of them.
Secondary sources also disagree on classification. VulDB labels the issue OS command injection (CWE-78). The CNA record, by contrast, assigns CWE-306, describes an unauthenticated command server, and discloses no command injection details. We treat the JetBrains CVE record as authoritative. The more specific secondary label should not be read as a confirmed exploit mechanism, and the public record does not support claims of arbitrary code execution.
Patch information
JetBrains fixed CVE-2026-133089 in two TeamCity On Premises bug fix releases, both published on 3 November 2026:
- 2026.2.x line: fixed in 2026.2.2, build 239308
- 2026.1.x line and earlier: fixed in 2026.1.6, build 223074
The CNA record matches these releases. JetBrains' Security Bulletin, filtered to TeamCity 2026.2.2, lists the issue as TW-104277, rated High and marked resolved in 2026.2.2,2026.1.6.
The fix is in the TFS helper and its plugin packaging. It is delivered as part of the full server releases above, not as a separate plugin update.
The release notes put the fix in context. The 2026.2.2 notes report 40 security problems fixed, and the 2026.1.6 notes report 38. There is one quirk. The bulletin link inside the 2026.1.6 notes points to the 2026.1.5 filter, but the bulletin entry itself lists 2026.1.6 as the fixed version.
Getting the fix. JetBrains' release post lists three ways to obtain these builds:
- The in-product automatic update. TeamCity documentation places this on the Admin, Updates page.
- Downloading the installer or archive from jetbrains.com.
- Pulling the updated Docker image.
All bug fix releases within a major version share a data format. Moving within the 2026.2.x or 2026.1.x line therefore needs no backup and restore. TeamCity's general upgrade documentation still recommends backing up data before any upgrade. Correctly installed agents upgrade automatically once the server is updated, and JetBrains warns not to interrupt that process.
No published workaround. We found no source documenting a temporary workaround for this CVE. Do not assume that disabling a TFS feature, changing a port, or adding a reverse proxy rule fixes this defect. JetBrains' general security notes recommend running TeamCity in a trusted environment without access by malicious users. That is general guidance, not a validated compensating control for CVE-2026-133089. If an affected instance cannot be updated promptly, seek guidance from JetBrains rather than inferring a mitigation.
Affected systems and versions
- Affected: every JetBrains TeamCity version below 2026.1.6.
- Affected: TeamCity 2026.2 up to, but not including, 2026.2.2.
- Still affected: installations on 2026.2.1 or 2026.1.5. These releases fixed only the network binding issue (CVE-2026-133057), not the missing authentication.
- Fixed: 2026.1.6 (build 223074) or later on the 2026.1 line, and 2026.2.2 (build 239308) or later on the 2026.2 line.
The vulnerable component is the native Windows TFS helper (tfs-native.exe, copied at runtime to TC-TFS-NATIVE-<digits>.exe), shipped in the TFS plugin tfs-support.jar. The CVE record does not specify whether other deployment editions or configurations are affected.
Vendor security history
JetBrains has built developer tools since 2000, and TeamCity is its continuous integration server. The vendor says TeamCity is trusted by more than 30,000 DevOps teams. That is JetBrains' own figure, not an independent measure.
The most relevant prior incident is CVE-2023-42793. CISA reported that the Russian Foreign Intelligence Service (SVR, also tracked as APT29) exploited it in internet-connected TeamCity servers, and that JetBrains patched it in September 2023. CISA described privilege escalation, lateral movement and additional backdoors following that exploitation. It also explained that a compromised TeamCity server can expose source code and signing certificates and enable tampering with build or deployment processes.
That history shows why TeamCity exposure matters, but it involves a different CVE and should not be transferred to CVE-2026-133089. For this CVE, the reviewed sources contain:
- No confirmed exploitation in the wild.
- No named threat actor.
- No public proof of concept.
Rapid7 reports that the CVE is not in the CISA Known Exploited Vulnerabilities catalog, and a threat tracking page reports no indexed exploitation evidence. These are limited signals, not proof of absence. NVD had not yet published its own assessment, so the 8.1 score is the JetBrains CNA score.
The TFS helper itself received three security fixes across two consecutive update cycles: the network binding issue (CVE-2026-133057), the missing authentication (CVE-2026-133089), and an XXE (TW-104134).
References
- NVD entry for CVE-2026-133089
- CVE Record: CVE-2026-133089
- CVE Services API record for CVE-2026-133089
- NVD entry (patch source link)
- CIRCL Vulnerability Lookup: CVE-2026-133089
- CIRCL Vulnerability Lookup: CVE-2026-133057
- JetBrains Fixed Security Issues
- JetBrains Security Bulletin filtered to TeamCity 2026.2.2
- TeamCity 2026.2.2 and 2026.1.6 Updates, The JetBrains Blog
- TeamCity 2026.2.2 Release Notes
- TeamCity 2026.1.6 Release Notes
- TeamCity 2026.2.1 and 2026.1.5 Are Out, The JetBrains Blog
- TeamCity Documentation: Applying Patches
- Upgrading TeamCity Server and Agents
- TeamCity Security Notes
- Team Foundation Version Control (Azure DevOps) in TeamCity
- CWE-306: Missing Authentication for Critical Function
- Rapid7 Vulnerability Database entry
- Threat Radar entry
- VulDB entry
- CISA Advisory AA23-347A: SVR Exploiting JetBrains TeamCity CVE Globally
- TeamCity product site
- JetBrains Corporate Overview



