Automated Threat Modeling

Brief Summary: JetBrains TeamCity CVE-2026-132891, Critical Remote Code Execution via External Pull Requests

A brief summary of CVE-2026-132891, a CVSS 9.8 remote code execution flaw in JetBrains TeamCity reachable through external pull requests and classified as CWE-696 (Incorrect Behavior Order). It covers the fixed releases and build numbers, how to verify your version, and vendor guidance for handling untrusted pull requests.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-19

Brief Summary: JetBrains TeamCity CVE-2026-132891, Critical Remote Code Execution via External Pull Requests

Introduction

JetBrains has fixed a critical flaw in TeamCity that made remote code execution possible through external pull requests, the contributions that arrive from forks and outside contributors rather than from trusted team members. The flaw has a CVSS 3.1 score of 9.8 and a vector that requires no privileges and no user interaction. Any organization whose TeamCity server builds code from repositories that outsiders can contribute to should treat this as a priority upgrade.

TeamCity is JetBrains' continuous integration server, used to build and test code from connected version control repositories. JetBrains states on its product page that more than 30,000 DevOps teams use TeamCity; that is a vendor claim rather than an independent market measurement. A CI server runs code from the repositories it watches, so the way it handles untrusted contributions matters for software supply chain security as well as for the server itself.

Technical information

What the record states

The CVE record describes the issue in one sentence: in JetBrains TeamCity before 2026.2, 2026.1.4 and 2025.11.8, remote code execution was possible via external pull requests. JetBrains' Fixed Security Issues bulletin lists it with the same title, "Remote code execution was possible via external pull requests", rated Critical, with internal tracker ID TW-102506 and credit to Antoni Tremblay.

The CVSS 3.1 vector is:

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

In plain terms, the attack is reachable over the network and has low complexity. It needs no privileges on TeamCity and no user interaction, and it has high impact on confidentiality, integrity and availability within an unchanged security scope.

Root cause: an ordering problem (CWE-696)

The weakness is classified as CWE-696, Incorrect Behavior Order. This class covers bugs where every required step exists but the steps run in the wrong order. A typical example is a security check that only runs after the risky action it is supposed to guard.

In TeamCity's case, the risky action is handling code from external pull requests. JetBrains has not said which steps were out of order. Reading the CWE against the CVE description, the likely shape is that some processing or execution of external pull request content happened before the server decided whether that pull request should be trusted. A fix for this class of bug normally moves the trust or authorization decision ahead of any action on the untrusted content, so nothing from an external pull request runs until it has passed that gate. This is an inference from the CWE, not a confirmed description of the code change.

Why external pull requests are a sensitive input

JetBrains' own Pull Requests documentation warns that builds of changes from public repositories, where untrusted users can contribute, may run malicious code on build agents. It advises against configuring VCS triggers and the Pull Requests build feature so that builds with unverified pull request changes start automatically. The Security Notes page makes the same point: pull requests from unknown or outside users may contain malicious code that runs on the build agent.

That documented risk is the general background, a configuration hazard administrators are expected to manage. CVE-2026-132891 is a different kind of problem. It is a vendor-confirmed product flaw, fixed in specific builds, in which the order of TeamCity's own behaviors allowed code execution. The available sources do not establish that the general documented risk is the precise exploit mechanism for this CVE.

Attack flow, as far as the sources support it

No exploit details have been published, so the following describes only what can be derived from the CVE description, CVSS vector and CWE:

  1. Entry point. The attacker interacts with TeamCity through an external pull request, meaning a contribution from a fork or an outside contributor to a repository that a TeamCity server processes.
  2. No TeamCity foothold required. The vector specifies PR:N and UI:N, so the attacker needs no TeamCity account or privileges, and no TeamCity user has to approve or click anything for the attack to work.
  3. Misordered handling. Based on CWE-696, TeamCity performed some action on the external pull request content before the step that should have decided whether that content was trusted.
  4. Outcome. The result is remote code execution with high confidentiality, integrity and availability impact.

Several things remain undocumented in the reviewed sources: the vulnerable code path, the specific endpoint or request format, any configuration prerequisite beyond processing external pull requests, the payload, and whether the code runs on the server or on a build agent and under which account. Treat any write-up claiming these details with caution until JetBrains or the credited researcher publishes them.

Patch information

Fixed releases

JetBrains fixed CVE-2026-132891 in TeamCity 2026.2, 2026.1.4 and 2025.11.8. All three builds were released on the same day, and you only need the one that matches your release line:

  • 2026.2 line (current major): first fixed version 2026.2, build 238924, released 2 Sep 2026
  • 2026.1.x line: first fixed version 2026.1.4, build 222865, released 2 Sep 2026
  • 2025.11.x and earlier: first fixed version 2025.11.8, build 208382, released 2 Sep 2026

Later builds on these lines also contain the fix, for example 2026.2.1 (build 239120, released 5 Oct 2026).

Vendor bulletin entry

The JetBrains Fixed Security Issues bulletin row for this CVE contains:

  • Title: Remote code execution was possible via external pull requests
  • Internal tracker ID: TW-102506
  • Credited to: Antoni Tremblay
  • Severity: Critical
  • Resolved in: 2026.2, 2026.1.4, 2025.11.8
  • Weakness: CWE-696 (Incorrect Behavior Order)

No public diff

TeamCity is closed source, so there is no public commit, pull request or diff for this fix. The tracker entry is not public either. A query to the YouTrack API returned:

Entity with id TW-102506 not found

That response is normal for security tickets. The fix is available only as vendor-built release binaries. The release notes do not name individual CVEs. The 2026.1.4 notes state that 94 security problems have been fixed, the 2025.11.8 notes say 76, and the 2026.2 notes say 130. Each points to the Security Bulletin, which JetBrains says is published a few days after a release. In this case the CVE went public on 19 Nov 2026, about 11 weeks after the fixed builds shipped on 2 Sep 2026. Teams that upgraded promptly in September were already protected before the CVE was disclosed.

Other vulnerabilities closed by the same upgrade

The bulletin credits several other TeamCity vulnerabilities to the same three releases:

  • RCE via a whitelist bypass in the build messages protocol (CVE-2026-111094)
  • A Kotlin DSL sandbox escape (CVE-2026-100253)
  • CRLF-based command injection in Pipeline Git settings (CVE-2026-100254)
  • Administrator account takeover via password reset (CVE-2026-100255)
  • Two stored XSS issues (CVE-2026-111095 and CVE-2026-111096)

Upgrading for CVE-2026-132891 closes all of these at once.

Verifying that you are patched

There is no source fix to backport, so the only check is the version and build number reported by the server. It should report one of the following or later:

  • 2026.2 (build 238924) or later
  • 2026.1.4 (build 222865) or later on the 2026.1 line
  • 2025.11.8 (build 208382) or later on the 2025.11 line

Interim controls from vendor documentation

If an upgrade has to wait, JetBrains' general guidance on untrusted pull requests reduces exposure. These are defense-in-depth measures, not a replacement for the fixed build:

  1. Do not configure VCS triggers and the Pull Requests build feature so that builds with unverified pull request changes start automatically.
  2. For incoming external pull requests, start builds manually after inspecting and verifying the changes, or configure Untrusted Builds to require additional review.
  3. Either disallow public pull request builds, or run them on separate, isolated, throwaway agents.

Affected systems and versions

According to the CVE record and the CNA affected ranges, the following TeamCity versions are vulnerable:

  • 2026.1 line: every 2026.1 build before 2026.1.4 (CNA range 2026.1 < 2026.1.4)
  • 2025.11 line and all earlier releases: every release before 2025.11.8 (CNA range 0 < 2025.11.8)
  • The CVE description also lists TeamCity before 2026.2 as affected, with 2026.2 as the fixed release on the current major line

Fixed: 2026.2 (238924), 2026.1.4 (222865), 2025.11.8 (208382), and later builds on each line.

The vulnerability is reached via external pull requests. The reviewed sources do not specify a more precise vulnerable configuration, so treat any affected server that processes pull requests from forks or outside contributors as in scope until it is upgraded.

Vendor security history

TeamCity has been a target in earlier, unrelated incidents. CISA advisory AA23-347a reported that Russian Foreign Intelligence Service (SVR) actors, also tracked as APT29, exploited CVE-2023-42793 against TeamCity servers globally beginning in September 2023. The CISA Known Exploited Vulnerabilities catalog also lists separate TeamCity authentication bypass and relative path traversal vulnerabilities.

That history is useful context for patch prioritization, but it does not tie CVE-2026-132891 to those actors. For this CVE, the reviewed intelligence page lists no public exploit or proof of concept and no associated threat actors, and no reviewed source establishes active exploitation. The absence of public reports is not proof that exploitation has not occurred.

JetBrains ships fixes in release builds whose notes give only counts of security problems fixed, then publishes CVE-level details in its Fixed Security Issues bulletin afterwards. For CVE-2026-132891 that gap was roughly 11 weeks, so release cadence, rather than CVE publication, is the more reliable trigger for TeamCity upgrades.

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