Automated Threat Modeling

Brief Summary: JetBrains TeamCity CVE 2026 132236, Pipeline YAML Path Traversal Leading to Remote Code Execution

A brief summary of CVE 2026 132236, a relative path traversal in the TeamCity pipeline YAML file path that allowed remote code execution by low-privileged users. Covers affected versions, the July 2026 fixed releases, and relevant TeamCity security history.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-18

Brief Summary: JetBrains TeamCity CVE 2026 132236, Pipeline YAML Path Traversal Leading to Remote Code Execution

Introduction

A path traversal in how JetBrains TeamCity resolves the pipeline YAML file path gave low-privileged users a route to remote code execution on a CI/CD server, the system that typically holds build secrets and drives what runs on build agents. The fix has been available since late July 2026, but the CVE ID was only published on 18 November 2026, so many teams are now seeing scanner alerts for a patch they may already have applied.

JetBrains is a developer tools company founded in 2000, and TeamCity is its CI/CD platform for triggering builds, investigating failures, and confirming fixes. JetBrains states that TeamCity is trusted by more than 30,000 DevOps teams, a vendor-reported figure rather than an independent market measurement. CI/CD servers sit between source code and production artifacts, so a flaw in one reaches well beyond the server itself.

Technical information

CVE 2026 132236 is classified as CWE 23, Relative Path Traversal. JetBrains, acting as the CNA, scores it CVSS 3.1 8.8 (High):

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

In plain terms, the attack works over the network, has low complexity, needs only low privileges and no user interaction, leaves scope unchanged, and has high impact on confidentiality, integrity, and availability. NVD currently displays the CNA score. Its own NIST assessment has not yet been provided.

Root cause

The official description is short: "Remote code execution was possible via path traversal in the pipeline YAML file path." The patch information gives a conceptual picture of what went wrong.

TeamCity Pipelines can read their YAML definition from a path in the source repository, such as the default .teamcity.yml. In affected builds, that path could contain relative traversal sequences like ../, which let the resolved file land outside the directory TeamCity intended to read from. Pipeline YAML defines what the server and build agents run, so whoever controls which file is treated as the pipeline definition has a path toward code execution.

A proper fix for this class of bug normalizes or canonicalizes the supplied path and rejects any result that falls outside the allowed checkout or settings root. Removing ../ substrings is not enough, because that approach is a well-known source of bypasses. JetBrains has not published how its fix is implemented. TeamCity is closed source, and there is no public commit, diff, or advisory text describing the code change, so we do not show any code here.

Attack flow

Based on the CVSS vector and the conceptual description, exploitation follows this general shape:

  1. The attacker holds a low-privileged TeamCity account with the ability to influence the pipeline YAML file path (the vector requires low privileges and no user interaction).
  2. The attacker supplies a pipeline YAML path containing relative traversal sequences such as ../.
  3. The affected TeamCity build resolves that path without confining it to the intended directory, so the file read as the pipeline definition comes from outside the expected location.
  4. Because the pipeline definition controls what the server and agents execute, this results in code execution.

The public record does not specify the exact file the traversal targets, the request sequence, the payload, or whether the resulting code runs on the server, an agent, or both. Those details are not public, and we do not speculate on them.

JetBrains tracks the issue internally as TW 102074 and credits Antoni Tremblay with the report.

Patch information

JetBrains fixed CVE 2026 132236 in two TeamCity On Premises maintenance releases, both published on 27 July 2026:

Release lineFixed versionBuildSecurity fixes in the release
2026.1.x2026.1.322274230
2025.11.x2025.11.720826422

The JetBrains Fixed Security Issues page lists the CVE as High severity with resolved versions 2026.1.3 and 2025.11.7, which matches the CNA record.

The timing gap. Neither release-notes page names TW 102074 or the pipeline YAML path. Each reports only a count of fixed security problems and points to the Security Bulletin, which JetBrains says usually follows a few days after a release. The CVE ID itself was not published until 18 November 2026. If you applied 2026.1.3 or 2025.11.7 when they shipped, you have had this fix for months.

The same releases also fixed the critical authentication bypass CVE 2026 63077 and two other TeamCity pipeline CVEs, CVE 2026 132235 and CVE 2026 132237. This fix shipped as one change inside a large security update rather than as a standalone hotfix.

How to upgrade. JetBrains offers three options:

  • The built-in automatic update
  • A fresh download from the JetBrains website
  • The updated TeamCity Docker image

Within the 2026.1.x line, 2026.1.3 uses the same data format as the other 2026.1.x releases, so you can move up or down within that series without a backup and restore. Later builds, including 2026.1.4 and newer and the 2026.2 line, also contain the fix. The reviewed materials do not describe any workaround or configuration-based compensating control, so upgrading is the supported mitigation.

Affected systems and versions

Per the CVE record, the following JetBrains TeamCity versions are affected:

  • 2026.1 releases before 2026.1.3
  • All versions before 2025.11.7

Fixed versions:

  • 2026.1.3 (build 222742) and later 2026.1.x builds
  • 2025.11.7 (build 208264)
  • The 2026.2 line

The fixed releases are TeamCity On Premises maintenance releases. The record lists no configuration conditions beyond the low-privilege requirement in the CVSS vector.

Vendor security history

TeamCity has been a target for capable adversaries before. CISA reported that a different flaw, CVE 2023 42793, was exploited at large scale by actors affiliated with the Russian Foreign Intelligence Service (SVR), also known as APT 29, CozyBear, and NOBELIUM. CISA noted that JetBrains issued a patch in mid-September 2023, after which the operation was limited to unpatched, internet-reachable TeamCity servers.

This history is context only. In the sources we reviewed, there is no substantiated report of in-the-wild exploitation or threat actor activity tied to CVE 2026 132236. A partial check of the CISA Known Exploited Vulnerabilities catalog (20 of 1,786 results) did not show the identifier, but that limited view cannot confirm absence from the full catalog.

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