External risk intelligence

JetBrains TeamCity Remote Code Execution via External Pull Requests

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-132891

JetBrains TeamCity is a continuous integration and continuous deployment (CI/CD) server typically deployed as a centralized, network-accessible service to manage build pipelines. These platforms are commonly configured with web interfaces that are reachable within an organization's network or exposed to the internet to facilitate remote access for developers and automated systems.

Remote Code Execution

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in JetBrains TeamCity allows for remote code execution through external pull requests, potentially enabling unauthorized access and control over development pipelines. This issue affects the underlying technology used for continuous integration and deployment, which is central to many software development processes. The main concern at this stage is confirming if the organization's TeamCity instances are exposed and potentially affected.

  • Code execution via pull requests.
  • Central to development pipeline security.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could initiate an attack by submitting an external pull request to a TeamCity instance. This pull request would target a vulnerable component within the TeamCity CI/CD server, potentially leading to remote code execution.

  • Requires an external pull request.
  • Triggered by a specially crafted pull request.
  • Allows an attacker to run arbitrary code.

Live Threat

Current exploitation, exposure, and threat context

In JetBrains TeamCity, remote code execution could be possible via external pull requests when supported by the advisory. This could affect the integrity and availability of the CI/CD server and any systems it manages.

  • CI/CD server integrity and availability.
  • Exposure via external pull requests.
  • Compromise of build pipelines.

Operational Fix

Recommended remediation, mitigation, and detection steps

Security and platform teams are likely responsible for addressing this critical vulnerability in JetBrains TeamCity, as it impacts CI/CD pipelines and often involves network-accessible services. The first practical step is to confirm the scope of affected TeamCity instances, assess their exposure and business criticality, identify the accountable owner for each instance, and then prioritize remediation based on risk.

  • Platform or security teams own the issue.
  • Verify TeamCity instance exposure and criticality.
  • Plan coordinated vendor-assisted remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is JetBrains TeamCity?

TeamCity is a continuous integration and continuous deployment server that automates the software building, testing, and deployment process. It acts as a central hub for developers to manage build pipelines, often serving as the bridge between source code repositories and production environments.

What does CVE-2026-132891 mean?

This CVE identifies a critical vulnerability involving an error related to how the application manages operations, classified as CWE-696: Incomplete Cleanup. In this specific case, it allows an unauthenticated attacker to achieve remote code execution, granting them the ability to run unauthorized commands on the server hosting the TeamCity software.

How is this vulnerability triggered?

The issue is triggered when an attacker submits a specially crafted external pull request to the TeamCity server. It is important to note that internal, legitimate pull requests within a trusted environment do not necessarily trigger this behavior; the risk specifically centers on the processing of external or untrusted requests that exploit the component's handling logic.

Is my TeamCity instance at risk?

According to Halo Surface Signal, TeamCity is typically deployed as a centralized service accessible over a network. If your instance is reachable from the internet, it faces a higher risk of being targeted by external pull requests compared to instances strictly isolated within a private, internal-only network.

Do I need to update my software immediately?

Your first step should be to inventory your organization's TeamCity instances to confirm which versions are in use. Once identified, assess the criticality of these instances and prioritize applying the vendor-provided updates to mitigate the risk of unauthorized code execution before planning further remediation.

References