Automated Threat Modeling

Quick Look: TeamCity CVE-2026-132233, Build Attribute Injection Leading to Remote Code Execution via Relative Path Traversal

A brief summary of CVE-2026-132233, a CVSS 9.9 remote code execution issue in JetBrains TeamCity caused by build attribute injection and classified as relative path traversal (CWE 23). Includes affected versions and patch information for the 2026.1.3 and 2025.11.7 fixed builds.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-18

Quick Look: TeamCity CVE-2026-132233, Build Attribute Injection Leading to Remote Code Execution via Relative Path Traversal

Introduction

Continuous integration servers execute work on behalf of many projects and users, so a flaw that lets a low-privileged account run code on the server itself affects far more than a single repository. JetBrains has fixed one such issue in TeamCity. CVE-2026-132233, scored CVSS 3.1 9.9, made remote code execution possible via build attribute injection in versions before 2026.1.3 and 2025.11.7.

JetBrains describes TeamCity as a CI/CD platform offered both as TeamCity On Premises and as TeamCity Cloud. Its product materials list integration with multiple source control systems, project hierarchy, role-based access control, agent pools, audit trails, and build chain management. That places TeamCity at the center of build and delivery workflows, although the sources we reviewed do not quantify its market share or customer base.

Technical information

Classification and scoring

The CVE record, published on November 18, 2026, describes the issue only as remote code execution via build attribute injection, and classifies it as CWE 23, Relative Path Traversal. The JetBrains CNA assigned the following CVSS 3.1 vector:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

In plain terms, the scoring indicates:

  • AV:N: reachable over the network
  • AC:L: low attack complexity
  • PR:L: low privileges required
  • UI:N: no user interaction
  • S:C: changed security scope
  • C:H/I:H/A:H: high impact to confidentiality, integrity, and availability

NVD repeats the 9.9 score and vector but had not supplied its own assessment at the time of review. These are scoring attributes, and they do not confirm implementation details. The records do not specify what kind of low privilege is required or which deployment configurations expose the vulnerable path.

Root cause (inferred from vendor classification)

TeamCity is closed source, the internal YouTrack ticket TW-101694 is not publicly accessible, and the release notes contain no technical detail. There is no public commit, diff, or vulnerable code to show. What follows is inferred from the vendor's own classification, not from vendor code:

  • The description names the entry point as an injected build attribute.
  • The CWE names the effect as relative path traversal.
  • Taken together, this suggests an attacker-supplied attribute value was later used to build a file path on the server, and sequences such as ../ were not rejected or normalized.

A fix for this class of bug typically ensures the attribute value cannot escape its intended directory, either by canonicalizing the path and confirming it remains inside the allowed base folder, or by rejecting path separators and traversal segments outright.

Attack flow (high level, based on the briefing)

  1. An attacker holds a low-privileged account on a vulnerable TeamCity server (consistent with PR:L).
  2. The attacker supplies a crafted value for a build attribute containing relative traversal sequences.
  3. The server uses that value to construct a file path without confining it to the expected directory.
  4. The resulting write lands outside the expected location, which leads to code running in the TeamCity server's context. This crossing from a build-level input into server-level execution is consistent with the changed scope (S:C).

The public sources do not document the specific endpoint, attribute name, payload format, or exact exploit chain, and we do not speculate on them here.

Patch information

JetBrains fixed CVE-2026-132233 in two TeamCity On Premises maintenance releases that shipped on 27 July 2026:

  • 2026.1.3 (build 222742) for the 2026.1 line
  • 2025.11.7 (build 208264) for the 2025.11 line

Because TeamCity is closed source, the patch is available only as the vendor's compiled builds. No public commit or pull request exists.

What the vendor record says

JetBrains' Fixed security issues bulletin lists the issue as "Remote code execution was possible via build attribute injection", tracked as TW-101694, rated Critical, resolved in 2026.1.3,2025.11.7, and classified as CWE 23. The affected ranges in the CVE record, as shown on NVD:

  • 2026.1.x branch: 2026.1 up to, but not including, 2026.1.3; first fixed build is 2026.1.3 (build 222742)
  • 2025.11.x and earlier: 0 up to, but not including, 2025.11.7; first fixed build is 2025.11.7 (build 208264)

The release notes for 2026.1.3 and 2025.11.7 report 30 and 22 security problems fixed, respectively, and the JetBrains release blog says each release addressed "more than 20 security vulnerabilities". Besides TW-101694, the same bulletin batch includes:

  • three other CWE 23 path traversal fixes, in project import archives, the pipeline YAML file path, and the external artifact cache (CVE-2026-132235, CVE-2026-132236, CVE-2026-132237)
  • argument injection RCE fixes in the Perforce and Mercurial VCS settings
  • the critical unauthenticated agent polling deserialization fix (CVE-2026-63077)

Installing either fixed build therefore closes this whole group of file path and injection bugs at once.

Obtaining the fixed builds

JetBrains distributes the fix as complete server builds via:

  • TeamCity's built-in automatic update
  • installers and tar.gz archives on the JetBrains download page
  • updated Docker images

Within a release line the data format does not change, so moving from an earlier 2026.1.x build to 2026.1.3 needs no backup and restore. Newer builds already exist on both lines (for example 2025.11.8, 2026.1.6, and 2026.2.x). They include this fix plus later security changes, so 2026.1.3 and 2025.11.7 are only the minimum versions that contain it.

The reviewed sources do not describe a temporary workaround or configuration change specific to this CVE.

Affected systems and versions

  • TeamCity 2026.1 line: 2026.1 up to, but not including, 2026.1.3. Fixed in 2026.1.3 (build 222742).
  • TeamCity 2025.11 line and earlier: all versions before 2025.11.7. Fixed in 2025.11.7 (build 208264).

The fixed releases are TeamCity On Premises maintenance builds. Beyond the version ranges above, the records do not identify specific configurations that are or are not exposed.

Vendor security history

TeamCity has been the subject of prior public advisories. In February 2024, CISA published an alert about a different TeamCity On Premises vulnerability, CVE-2024-23917, stating that it could allow a cyber threat actor to take control of an affected system and advising users and administrators to apply the update or workarounds. A single prior alert is not enough to characterize JetBrains' overall security track record, and the sources we reviewed do not establish a broader pattern.

For this CVE, the reviewed sources do not identify active exploitation, a named threat actor, a campaign, or a public exploit. That leaves exploitation status unknown from these sources, not confirmed absent.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization