SecPod

Learn Search

Search across all Learn content

← Back to Security Research
Four Critical CVEs on 19 November Enable Remote Code Execution in JetBrains TeamCity CI/CD Servers

Four Critical CVEs on 19 November Enable Remote Code Execution in JetBrains TeamCity CI/CD Servers

Nov 20, 2026By Pranav M Rao5 min read

Overview

JetBrains has disclosed four Critical remote code execution vulnerabilities affecting TeamCity On-Premises: CVE-2026-132231, CVE-2026-132232, CVE-2026-132233, and CVE-2026-132234. The vulnerabilities affect Perforce integration settings, build attributes, and Mercurial VCS root settings.

Each vulnerability has a CVSS 3.1 score of 9.9 (Critical). The common vector, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, indicates network-based exploitation with low attack complexity, low privileges, and no user interaction. Successful exploitation could enable code execution in the affected TeamCity environment and cause severe confidentiality, integrity, and availability impacts.

These vulnerabilities are not authentication bypasses. Their CVSS vectors indicate that an attacker requires a low-privileged TeamCity account or equivalent authorized access to reach the affected functionality. JetBrains has not publicly documented the precise code-execution context, payload format, or end-to-end exploitation procedure for each vulnerability.

JetBrains fixed the vulnerabilities in TeamCity 2026.1.3 and 2025.11.7, released on 27 July 2026. The four CVE records were subsequently published on 18 November 2026. Organizations running older TeamCity releases should upgrade to a currently supported version without delay.

Background

JetBrains TeamCity is a continuous integration and continuous delivery platform used to build, test, package, and deploy software. A TeamCity server commonly stores source-control credentials, build parameters, deployment secrets, signing material, access tokens, and connections to production infrastructure.

This makes TeamCity a high-value security target. Code execution in a TeamCity environment could provide access to sensitive build data or allow interference with software-building and delivery workflows. The actual effect depends on the permissions assigned to TeamCity, the affected project, connected version-control systems, build agents, stored secrets, and deployment integrations.

The four vulnerabilities affect inputs associated with Perforce, Mercurial, and TeamCity build configuration. They involve best-fit character mapping, argument injection, and build attribute injection. Improperly handled configuration values could cross a trust boundary and reach an execution-sensitive operation.

Vulnerability Details

CVE ID Affected Functionality Vulnerability Type CVSS EPSS CISA KEV Fixed Versions
CVE-2026-132231 Perforce settings Remote code execution through best-fit character mapping (CWE-1289) 9.9 Critical 0.65% No 2026.1.3 and 2025.11.7
CVE-2026-132232 Perforce settings Remote code execution through argument injection (CWE-88) 9.9 Critical 0.69% No 2026.1.3 and 2025.11.7
CVE-2026-132233 Build attributes Remote code execution through build attribute injection (CWE-23) 9.9 Critical 0.70% No 2026.1.3 and 2025.11.7
CVE-2026-132234 Mercurial VCS root settings Remote code execution through argument injection (CWE-88) 9.9 Critical 0.70% No 2026.1.3 and 2025.11.7

EPSS scores were assessed on 20 November 2026 and may change over time. None of the four vulnerabilities was listed in the CISA Known Exploited Vulnerabilities catalog at the time of assessment.

Disclosure and Patch Timeline

Date Event
27 July 2026 JetBrains released TeamCity 2026.1.3 and 2025.11.7. These maintenance releases contained fixes for the four vulnerabilities.
18 November 2026 CVE-2026-132231, CVE-2026-132232, CVE-2026-132233, and CVE-2026-132234 were publicly published.
20 November 2026 None of the four vulnerabilities was listed in the CISA KEV catalog, and no confirmed exploitation in the wild had been publicly reported.

Technical Analysis

JetBrains publicly confirms that all four vulnerabilities could enable remote code execution in affected TeamCity versions. However, the vendor's descriptions do not disclose the precise payload structure, internal code path, operating-system command, or execution context associated with each issue.

CVE-2026-132231: Best-Fit Character Mapping in Perforce Settings

CVE-2026-132231 affects the handling of Perforce configuration values. JetBrains describes the issue as remote code execution through best-fit character mapping and classifies it under CWE-1289.

Best-fit character conversion may replace a character that cannot be represented in a target character set with a visually or functionally similar character. When this conversion occurs near a command, argument, path, or another security-sensitive boundary, the transformed value may not preserve the assumptions made during validation.

JetBrains has not published enough technical detail to state which characters, operating systems, command-construction routines, or execution functions are involved. The supported conclusion is that specially formed Perforce settings could enable code execution in the affected TeamCity environment.

CVE-2026-132232: Argument Injection in Perforce Settings

CVE-2026-132232 is an argument-injection vulnerability affecting Perforce settings. Argument injection occurs when attacker-controlled input is incorporated into a command or tool invocation without sufficient separation between configuration data and executable arguments.

A low-privileged attacker who can reach the affected configuration path could potentially supply a crafted value that changes how a downstream Perforce-related operation is interpreted. Successful exploitation could lead to code execution in the affected TeamCity environment.

The available disclosure does not establish which Perforce option is affected, what command is invoked, or the precise privilege context of resulting execution.

CVE-2026-132233: Build Attribute Injection

CVE-2026-132233 affects the processing of TeamCity build attributes. JetBrains confirms that build attribute injection could result in remote code execution in versions earlier than the fixed releases.

Build metadata can pass through multiple processing stages, including parameter substitution, configuration parsing, agent communication, and build execution. If an attacker-controlled attribute crosses into an execution-sensitive context without adequate validation, it may alter the intended operation.

JetBrains has not disclosed the affected attribute, parser, component, or final execution mechanism. The vulnerability should therefore not be associated with a specific command interpreter or TeamCity process identity without additional supporting evidence.

CVE-2026-132234: Argument Injection in Mercurial VCS Root Settings

CVE-2026-132234 affects Mercurial VCS root settings. A crafted value placed in the affected configuration could be interpreted as an additional argument when TeamCity performs a Mercurial-related operation.

Successful exploitation could lead to code execution in the affected TeamCity environment. The public disclosure does not identify the exact Mercurial option, internal invocation path, resulting operating-system command, or execution privilege level.

Potential Attack Methodology

The following stages describe a plausible exploitation scenario based on the CVSS requirements and affected functionality. JetBrains has not documented this as an observed attack chain.

Phase 1: Low-Privileged TeamCity Access

The attacker obtains a low-privileged TeamCity account or equivalent authorized access to configuration functionality associated with the vulnerable code path.

Phase 2: Vulnerable Functionality Identified

The attacker identifies an accessible Perforce setting, Mercurial VCS root setting, or build-attribute operation affected by one of the four vulnerabilities.

Phase 3: Crafted Value Submitted

A specially formed configuration value is submitted to trigger character-conversion, argument-handling, or attribute-processing behavior.

Phase 4: Security Boundary Crossed

The crafted value reaches an execution-sensitive operation and is interpreted differently from the value originally expected by the application.

Phase 5: Code Execution

Successful exploitation could enable code execution in the affected TeamCity environment. JetBrains has not publicly established the precise execution context for each CVE.

Phase 6: Potential CI/CD Impact

Depending on TeamCity permissions and connected resources, subsequent activity could affect build data, source-control integrations, artifacts, secrets, or delivery workflows. These outcomes are potential consequences and have not been reported as observed exploitation.

Indicators of Compromise (IOCs)

JetBrains has not published campaign-specific IP addresses, domains, file hashes, malicious payloads, account names, or other confirmed indicators of compromise for these four vulnerabilities.

The presence of an affected TeamCity version establishes vulnerability exposure, not evidence of compromise. Detection should focus on unusual configuration activity and unexpected behavior occurring around Perforce, Mercurial, and build-attribute processing.

Detection and Investigation Considerations

  • Review TeamCity audit activity: Examine recent changes to Perforce settings, Mercurial VCS roots, project configuration, and build attributes, particularly changes made by low-privileged or unfamiliar accounts.
  • Inspect authentication records: Investigate newly created accounts, unexpected access-token use, abnormal logins, and access from unfamiliar IP addresses.
  • Review build configuration history: Search for unexpected parameters, unusual encoded content, command-like values, character substitutions, or unexplained changes immediately before abnormal build behavior.
  • Monitor TeamCity-related process activity: Investigate unexpected child processes or operating-system commands associated with TeamCity components. Such behavior is a detection lead, not a vendor-confirmed IOC for these vulnerabilities.
  • Check source-control activity: Review Perforce and Mercurial authentication, repository access, and configuration changes for actions inconsistent with the initiating user.
  • Inspect secrets and integrations: If suspicious activity is identified, review the use of stored VCS credentials, deployment tokens, cloud credentials, signing material, and external service connections.
  • Validate the running TeamCity build: Confirm that the active server is TeamCity 2026.1.3, 2025.11.7, or a later supported release rather than relying only on downloaded package or deployment records.

MITRE ATT&CK Mapping

No confirmed exploitation campaign or observed post-exploitation behavior has been publicly documented for these vulnerabilities. Remote code execution alone does not establish which ATT&CK techniques an attacker used. Unsupported mappings are therefore marked as N/A.

Tactic Technique Technique ID Assessment
Reconnaissance N/A N/A No documented reconnaissance activity
Resource Development N/A N/A No documented attacker preparation
Initial Access N/A N/A The CVSS vectors require low privileges, and no confirmed initial-access procedure has been documented.
Execution N/A N/A JetBrains confirms remote code execution but does not document a command interpreter, script engine, or observed execution procedure.
Persistence N/A N/A No documented persistence activity
Privilege Escalation N/A N/A No documented privilege-escalation procedure
Stealth N/A N/A No documented stealth activity
Defense Impairment N/A N/A No documented security-control impairment
Credential Access N/A N/A No documented credential-access activity
Discovery N/A N/A No documented discovery activity
Lateral Movement N/A N/A No documented lateral movement
Collection N/A N/A No documented collection activity
Command and Control N/A N/A No documented command-and-control activity
Exfiltration N/A N/A No documented data-exfiltration activity
Impact N/A N/A No confirmed exploitation impact observed in the wild

Hypothetical Attack Flow

The following diagram represents a potential exploitation path inferred from the CVSS requirements and vulnerable functionality. It is not an observed attack sequence reported by JetBrains.

1 Low-Privileged TeamCity Access

An attacker obtains authorized, low-privileged access to an affected TeamCity instance.

2 Vulnerable Configuration Path Reached

The attacker reaches affected Perforce settings, Mercurial VCS root settings, or build-attribute functionality.

3 Crafted Value Submitted

A malicious configuration value targets character mapping, argument handling, or attribute processing.

4 Unsafe Interpretation

The value reaches an execution-sensitive operation and is interpreted differently from ordinary configuration data.

5 Code Execution in the TeamCity Environment

Successful exploitation could enable code execution in the affected TeamCity environment. The precise execution context is not publicly established.

6 Potential CI/CD Environment Impact

The attacker could potentially target accessible build data, secrets, artifacts, repositories, or deployment integrations. These outcomes have not been confirmed as observed exploitation.

Mitigation and Recommended Actions

  • Upgrade TeamCity immediately: Update affected installations to TeamCity 2026.1.3, 2025.11.7, or a later supported version. Because newer maintenance releases are available, administrators should preferably deploy the latest compatible supported release.
  • Verify the active version: Confirm the version and build number reported by the running TeamCity server after upgrading. Do not rely only on the downloaded installer, container tag, or package inventory.
  • Include secondary and test servers: Inventory production, staging, testing, disaster-recovery, and temporarily deployed TeamCity instances. Forgotten CI/CD systems may retain sensitive credentials and integrations.
  • Restrict network exposure: Limit TeamCity access to approved administrative networks, trusted users, or authenticated gateways. Avoid exposing administrative and project configuration interfaces directly to the internet.
  • Apply least privilege: Review which users can create or modify projects, VCS roots, Perforce and Mercurial settings, build configurations, and build parameters.
  • Audit recent configuration changes: Examine Perforce settings, Mercurial VCS roots, and build attributes modified before patching. Investigate unexplained or command-like configuration values.
  • Rotate exposed credentials when compromise is suspected: Rotate affected VCS credentials, TeamCity tokens, deployment secrets, cloud credentials, signing keys, and other secrets accessible to the affected environment.
  • Investigate before restoring service: If suspicious execution or unauthorized configuration activity is identified, isolate the server, preserve relevant logs, determine the scope of access, and rebuild the environment where integrity cannot be established.

Official References

Key Takeaways

  • Four TeamCity vulnerabilities affecting Perforce, Mercurial, and build attributes carry a CVSS score of 9.9.
  • Exploitation requires low privileges but does not require user interaction and could enable code execution in the affected TeamCity environment.
  • JetBrains fixed the vulnerabilities in TeamCity 2026.1.3 and 2025.11.7, released on 27 July 2026.
  • The CVE records were published on 18 November 2026, several months after the fixed releases became available.
  • No confirmed active exploitation, public proof of concept, malware campaign, or CISA KEV listing had been reported at the time of publication.
  • Organizations should upgrade to the latest supported TeamCity version, review recent configuration changes, and rotate credentials if compromise is suspected.

Instantly Fix Risks in Endpoints & Cloud with Saner

Saner is a continuous and integrated vulnerability and exposure management platform that helps organizations identify vulnerable software, prioritize critical exposure, deploy security updates, and verify remediation across endpoints and cloud workloads.

Schedule a Demo

Featured Posts

Open Adobe Animate CVE-2026-114938: Dependency Patch and Exploitation Analysis - November 19, 2026
Adobe Animate CVE-2026-114938: Dependency Patch and Exploitation Analysis - November 19, 2026

CVE Research

Adobe Animate CVE-2026-114938: Dependency Patch and Exploitation Analysis - November 19, 2026

Adobe APSB26-208 addresses CVE-2026-114938 through an Oracle JDK dependency update in Adobe Animate. This analysis covers affected Windows and macOS versions, the Java4Shell proof of concept, reported probing, technical prerequisites, and verified patch guidance - without assuming an Adobe-specific exploit.

Nov 20, 2026

Open PHP November 2026: 7 Critical-Priority Vulnerabilities and Remote Code Execution Risks
PHP November 2026: 7 Critical-Priority Vulnerabilities and Remote Code Execution Risks

CVE Research

PHP November 2026: 7 Critical-Priority Vulnerabilities and Remote Code Execution Risks

PHP's November 2026 security update addresses 7 vulnerabilities affecting Remote Code Execution Risks, and fixes.

Nov 20, 2026

Open Critical RCE CVE-2026-132891 Threatens JetBrains TeamCity Through External Pull Requests in November 19, 2026 Disclosure
Critical RCE CVE-2026-132891 Threatens JetBrains TeamCity Through External Pull Requests in November 19, 2026 Disclosure

CVE Research

Critical RCE CVE-2026-132891 Threatens JetBrains TeamCity Through External Pull Requests in November 19, 2026 Disclosure

JetBrains TeamCity faces a broad set of 181 CVE disclosures, led by critical CVE-2026-132891 (CVSS 9.8), an unauthenticated remote code execution flaw involving external pull requests. Explore affected versions, CI/CD security risks, and fixes.

Nov 20, 2026

Open 4EverAble2Shell: From a Security Hotfix to Root Compromise
vulnerability research4EverAble2Shell: From a Security Hotfix to Root Compromise

CVE Research

4EverAble2Shell: From a Security Hotfix to Root Compromise

Nov 20, 2026