External risk intelligence

JetBrains TeamCity Build Attribute Injection Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-132233

JetBrains TeamCity is a continuous integration and continuous delivery server. These platforms are commonly deployed as web-based services accessible to developers and build agents across network boundaries, frequently serving as centralized management hubs for software development lifecycles, which places them in common internet-facing or edge-reachable deployment patterns.

Path Traversal

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 has been identified in JetBrains TeamCity, a widely used platform for software development and deployment. This flaw could allow unauthorized remote code execution, potentially impacting the integrity and availability of development pipelines. The primary concern at this stage is to confirm if our environment utilizes the affected technology.

  • Attackers can run unauthorized code remotely.
  • Protects software development and deployment integrity.
  • Verify if TeamCity is in use within our systems.

Attack Path

How an attacker could exploit the issue

An attacker with some level of authenticated access to JetBrains TeamCity could potentially inject malicious code through a build attribute. This could allow them to execute arbitrary commands on the server, leading to a compromise of the system.

  • Requires authenticated access.
  • Triggered via build attribute injection.
  • Enables remote code execution.

Live Threat

Current exploitation, exposure, and threat context

A critical vulnerability in JetBrains TeamCity could allow an attacker with low privileges to execute arbitrary code remotely. This could occur when an attacker injects malicious code into build attributes, potentially impacting the integrity and confidentiality of the server and its associated data.

  • Build attributes and server configurations.
  • Via specially crafted build attribute injection.
  • Remote code execution and system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in JetBrains TeamCity requires a coordinated response, likely involving platform or infrastructure teams responsible for the CI/CD environment and the application owners who rely on its services. The immediate priority is to identify all instances of TeamCity, determine their exposure (especially external reachability), and confirm their criticality to business operations. Once these factors are understood, the accountable owner can plan and execute remediation, prioritizing systems with the highest risk.

  • Ownership: Platform or application owners.
  • Verify: External reachability and criticality.
  • Action: Plan and execute 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 delivery (CI/CD) server used by development teams to automate software building, testing, and deployment. It serves as a central hub where code changes are integrated and managed, often coordinating interactions between developers and various build agents to streamline the software development lifecycle.

What does CVE-2026-132233 mean by build attribute injection?

This vulnerability involves a weakness class known as CWE-23, which relates to path traversal or improper input handling. In the context of this CVE, it allows an attacker to manipulate build attributes—the data fields that define how a project is built—to inject malicious instructions. Because the system improperly validates these inputs, it may treat the injected data as executable commands, leading to remote code execution.

Does any interaction with TeamCity trigger this bug?

No, this is not triggered by casual browsing or unauthenticated access. The vulnerability requires the attacker to have at least low-level authenticated access to the TeamCity platform. Without valid credentials to interact with the build configuration processes, an attacker cannot successfully inject the malicious attributes needed to execute arbitrary code.

Why does Halo Surface Signal categorize this as an external threat?

Halo Surface Signal identifies this as an external risk because TeamCity instances are often deployed as web-based services accessible across network boundaries. These platforms frequently serve as centralized management hubs for developers and build agents, making them common targets for edge-reachable or internet-facing deployment patterns where network access can be broader than intended.

How should I respond if I am running TeamCity?

Your first step is to perform an inventory to identify all instances of TeamCity within your environment. Once identified, evaluate the network reachability of each instance to determine if it is internet-facing or internal. Coordinate with the platform owners to assess the criticality of these servers, then prioritize the application of official vendor patches to remediate the vulnerability in affected versions.

References