Automated Threat Modeling

Brief Summary: JetBrains TeamCity CVE-2026-132237, Path Traversal to Remote Code Execution in the External Artifact Cache

A brief summary of CVE-2026-132237, a CWE-23 relative path traversal in the TeamCity external artifact cache that enabled remote code execution, with affected versions and patch information for 2026.1.3 and 2025.11.7.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-18

Brief Summary: JetBrains TeamCity CVE-2026-132237, Path Traversal to Remote Code Execution in the External Artifact Cache

Introduction

According to JetBrains and the CNA-supplied NVD record, a path traversal flaw in the external artifact cache of JetBrains TeamCity made remote code execution possible on affected servers. A CI/CD server typically holds source code, build secrets, and deployment credentials. Code execution on the TeamCity server therefore puts much of an organization's software delivery pipeline within reach of whoever achieves it.

TeamCity is the CI/CD platform from JetBrains, offered for on-premises, hosted cloud, and hybrid deployment. JetBrains states that it is trusted by more than 30,000 DevOps teams. That is a vendor-reported adoption figure, not an independent market measurement. TeamCity servers have been targeted before, most notably through CVE-2023-42793, which CISA reported was exploited by Russian SVR-affiliated actors, so new TeamCity RCE issues tend to warrant prompt attention from defenders.

Technical information

Root cause

The JetBrains Fixed security issues bulletin describes the bug in a single line: Remote code execution was possible via path traversal in the external artifact cache. The issue is classified as CWE-23 (Relative Path Traversal) and tracked internally as TW-102075. Antoni Tremblay reported it.

CWE-23 bugs occur when an application takes a path segment influenced by the user (for example ../../), joins it onto a trusted base directory, and then reads or writes the resulting file without checking that the resolved path still sits inside that base. In this case the trusted base is the TeamCity external artifact cache. Because the stated impact is remote code execution, the traversal most plausibly allowed an attacker to write files into a location that the server later executes or loads. This is an inference from the vulnerability class and impact, not a confirmed description of the vulnerable code.

TeamCity On Premises is closed source, and the TW-102075 ticket is not publicly readable (a YouTrack REST lookup returned not found, which is normal for embargoed security tickets). There is no public commit, diff, or vulnerable code excerpt to review, and JetBrains has not published implementation details beyond the one-line description.

CVSS breakdown

The CNA (JetBrains s.r.o.) assigned a CVSS 3.1 base score of 8.8 High with the following vector:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
  • Attack Vector: Network. The flaw is reachable remotely.
  • Attack Complexity: Low. No special conditions are indicated.
  • Privileges Required: Low. An attacker needs some level of access. Without further evidence, this should not be described as an unauthenticated flaw.
  • User Interaction: None.
  • Scope: Unchanged.
  • Confidentiality, Integrity, Availability: High.

NVD lists the CNA score and vector. Its own assessment had not yet been provided at the time of review.

Likely attack flow

Based on the vulnerability class, the CVSS vector, and the stated impact, an attack would generally take the shape below. This is a reasoned outline, not a confirmed exploitation procedure.

  1. An attacker holding low privileges on the TeamCity server reaches it over the network.
  2. The attacker supplies a path value containing relative traversal sequences such as ../../ to an operation handled by the external artifact cache.
  3. The server joins that value onto the cache base directory and performs a file operation without confirming the resolved path stays within the cache root.
  4. The file operation lands outside the cache. If it places attacker-controlled content where the server later executes or loads it, the result is code execution on the server.

Open questions

The public records do not specify:

  • the exact request, endpoint, or cache path that triggers the traversal
  • whether a particular TeamCity configuration or permission level is required beyond low privileges
  • the execution context of any resulting code
  • vulnerability-specific indicators of compromise

The same builds fixed two other path traversal bugs from the same researcher that also led to RCE: CVE-2026-132235 (project import archives, TW-102020) and CVE-2026-132236 (pipeline YAML file path, TW-102074). Taken together, this suggests JetBrains reviewed path handling across several file-handling subsystems in this release cycle, not only the artifact cache.

Patch information

JetBrains fixed CVE-2026-132237 in TeamCity 2026.1.3 (build 222742) and TeamCity 2025.11.7 (build 208264). Both maintenance releases shipped on 27 July 2026. The fix is delivered only as a binary release.

The JetBrains bulletin rates the issue High, classifies it as CWE-23, and marks it resolved in 2026.1.3, 2025.11.7.

What the fix is expected to do

The standard remediation for this class of bug is to:

  1. Resolve the requested path to its canonical (normalized) form.
  2. Check that the canonical path still begins with the canonical cache root.
  3. Reject .. segments, absolute paths, and unusual separators or encodings before any file operation.

This is the typical pattern for CWE-23 fixes. JetBrains has not published its code change, so the list above is not a confirmed description of it.

Release context

The fix is part of a large, security-focused batch rather than a standalone hotfix:

  • The 2026.1.3 release notes report 30 security problems fixed, and the 2025.11.7 notes report 22.
  • The JetBrains release blog describes both updates as primarily focused on security, each addressing more than 20 vulnerabilities, including the critical CVE-2026-63077.

Obtaining the fixed builds

According to JetBrains, the patched builds are available through:

  • the in-product automatic update
  • installers and archives from the JetBrains download site
  • the updated jetbrains/teamcity-server Docker images

On the 2026.1 line, 2026.1.3 uses the same data format as every other 2026.1.x release, so administrators can move to it, or back, within that series without a backup and restore.

No vendor workaround has been published for this CVE. The JetBrains TeamCity security notes (trusted environment, per-project authorization, restricted deployment build permissions, a protected TeamCity Data Directory, disposable network-protected build agents, controlled agent OS user permissions, agents connected only to a trusted server, HTTPS for the web interface) remain useful hardening. They are general guidance, though, and do not mitigate this specific issue.

Affected systems and versions

Per the CNA-supplied NVD record:

  • 2026.1.x branch: TeamCity 2026.1 up to, but not including, 2026.1.3. First fixed build: 2026.1.3 (build 222742).
  • 2025.11.x and earlier: all versions before 2025.11.7. First fixed build: 2025.11.7 (build 208264).
  • 2026.2 line: NVD lists no affected range.
  • Later builds on each branch, such as 2026.1.4 and 2025.11.8, come after the fixed versions and fall outside the affected ranges.

The public records do not identify any specific vulnerable configuration beyond the version ranges and the low-privilege requirement in the CVSS vector.

Vendor security history

TeamCity has a record of serious vulnerabilities that attracted real-world exploitation:

  • CVE-2023-42793: CISA reported exploitation by Russian SVR-affiliated actors, also known as APT29, the Dukes, CozyBear, and NOBELIUM or Midnight Blizzard, since September 2023.
  • CVE-2024-27198 and CVE-2024-27199: both appear in the TeamCity-filtered CISA Known Exploited Vulnerabilities (KEV) listing, alongside CVE-2023-42793.
  • CVE-2026-63077: JetBrains reported active and attempted exploitation against unpatched TeamCity servers, and CISA added it to the KEV catalog. JetBrains did not name a threat actor.

For CVE-2026-132237 itself, the sources we reviewed confirm neither active exploitation nor threat actor attribution, and the CVE does not appear in the TeamCity-filtered KEV listing we reviewed. The exploitation status of CVE-2026-63077 should not be transferred to this issue. On the maintenance side, the 2026.1.3 and 2025.11.7 releases together fixed dozens of security problems. That shows active security maintenance, but it does not by itself measure overall product security quality.

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