Introduction
A critical argument injection flaw in the Perforce integration of JetBrains TeamCity allowed an authenticated user with low privileges to achieve remote code execution on the TeamCity server. Because TeamCity sits in the build and delivery workflow and the CVSS vector records a changed scope, the bug's impact extends beyond the application to the host it runs on. The 9.9 Critical rating reflects this.
TeamCity is JetBrains' CI/CD platform, and Perforce is one of its supported version control integrations. JetBrains, which is also the CNA that assigned this CVE, shipped the fix in TeamCity 2026.1.3 and 2025.11.7 on 27 July 2026. The CVE record itself was published on 18 November 2026.
Technical information
Root cause
TeamCity talks to Perforce by running the p4 command-line client. It builds the p4 command from values stored in the VCS root and connection settings, such as:
- the server port
- the user
- the workspace (client) name
- the stream
The weakness is classified as CWE-88, improper neutralization of argument delimiters in a command. In this class of bug, the child program reads a value meant to be a single data argument as an option instead. Typical triggers are a value that begins with the dash character used for command-line flags, or a value containing delimiters that split it into additional arguments.
The p4 client accepts options that change its behavior, so an authenticated user who can edit Perforce settings could make the TeamCity server run attacker-chosen code. The public record does not identify which setting field, which p4 options, or which configuration conditions are involved, and we do not speculate on those details here.
Severity breakdown
The CVSS 3.1 vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H:
- AV:N / AC:L: reachable over the network with low attack complexity
- PR:L: low privileges are required, so this is not an unauthenticated flaw. The record does not spell out the exact permission prerequisite beyond the vendor's description of a user who can edit Perforce settings
- UI:N: no user interaction is needed
- S:C: scope is changed, meaning impact reaches beyond TeamCity to the host
- C:H / I:H / A:H: high impact to confidentiality, integrity and availability
The CVE record's CISA SSVC enrichment rates the technical impact as "total".
Attack flow
Based on the vendor and CVE descriptions, exploitation follows this general sequence:
- The attacker holds an authenticated TeamCity account with permission to edit Perforce settings (a VCS root or connection).
- The attacker sets one of the values that TeamCity passes to
p4to content crafted so that it is parsed as an option, or split into extra arguments, instead of being treated as a single data value. - When TeamCity invokes the
p4client with those settings, the injected option reaches the command line. - The injected option changes the behavior of
p4in a way that results in execution of attacker-chosen code on the server host.
Related fix: CVE-2026-132231
The same JetBrains bulletin lists CVE-2026-132231 (TW-101693, CWE-1289), described as "Remote code execution was possible via best fit character mapping in Perforce settings". With best-fit mapping, Windows converts Unicode characters into look-alike ANSI characters. A full-width hyphen or quotation mark, for example, can become a real ASCII dash or double quote after a filter has already checked the input. Both CVEs were fixed in the same releases, so JetBrains hardened the whole path from Perforce settings to the command line against direct argument injection and encoding-based bypasses alike. Upgrading addresses both issues.
Patch information
JetBrains fixed this vulnerability in:
- TeamCity 2026.1.3 (build 222742)
- TeamCity 2025.11.7 (build 208264)
Both were released on 27 July 2026. JetBrains' security bulletin, which NVD links to as the CNA reference, lists CVE-2026-132232 as "Remote code execution was possible via argument injection in Perforce settings", rates it Critical, classifies it as CWE-88, tracks it internally as TW-101817, and gives 2026.1.3 and 2025.11.7 as the fixed versions.
What the fix does. The fix makes TeamCity treat Perforce setting values strictly as data before they reach the p4 command line. JetBrains has not published implementation details. The usual approach for this bug class is to validate or reject values that start with option prefixes or contain argument delimiters, and to pass values in positions where they cannot be read as flags.
How the fix is delivered. TeamCity on premises is closed source, so there is no public commit, diff or standalone hotfix plugin for this CVE. The fix ships only in full product releases. These were security-focused maintenance updates: the release notes count 30 security problems fixed in 2026.1.3 and 22 in 2025.11.7, and JetBrains' release post says the updates cover more than 20 vulnerabilities each, including the critical unauthenticated RCE CVE-2026-63077.
JetBrains documents three upgrade routes:
- the built-in automatic update feature
- installers and archives from the JetBrains download site
- the updated
jetbrains/teamcity-serverDocker image
TeamCity 2026.1.3 uses the same data format as other 2026.1.x builds, so moving within that series does not require a backup and restore step. Later builds in each series, such as 2025.11.8 and 2026.1.4 and newer, also include this fix. After updating, confirm the running version. The reviewed sources do not identify a separate workaround or temporary configuration mitigation, and the lack of one should not be read as evidence that an unpatched installation is safe.
Affected systems and versions
Per the NVD/CNA record, the affected ranges are:
- TeamCity 2026.1 up to but not including 2026.1.3 (
2026.1 <= version < 2026.1.3) - All TeamCity versions before 2025.11.7 (
version < 2025.11.7)
Fixed versions:
- 2026.1.3 (build 222742) and later in the 2026.1 series
- 2025.11.7 (build 208264) and later in the 2025.11 series
The vulnerable path runs through Perforce settings, so the relevant attack surface is any authenticated account able to edit Perforce VCS roots or connections. The record does not describe further configuration conditions.
Vendor security history
TeamCity has a documented history of being targeted. CISA advisory AA23-347A reported that Russian SVR-affiliated actors, also tracked as APT29 and NOBELIUM/Midnight Blizzard, exploited TeamCity CVE-2023-42793, an authorization bypass leading to arbitrary code execution, at large scale beginning in September 2023. CISA's Known Exploited Vulnerabilities catalog also lists TeamCity CVE-2024-27199.
That history shows prior exploitation of TeamCity flaws, but it does not establish exploitation of CVE-2026-132232 or implicate those actors. For this CVE, the record's CISA SSVC enrichment lists exploitation as "none" and automatable as "no" at the time of assessment, and the TeamCity entries in the KEV catalog material we reviewed did not include CVE-2026-132232. We found no public exploit or threat actor attribution.
References
- NVD entry for CVE-2026-132232
- CVE.org record for CVE-2026-132232
- CVE Services API record (cveawg.mitre.org)
- JetBrains fixed security issues
- JetBrains fixed security issues, TeamCity 2026.1.3
- TeamCity 2026.1.3 release notes
- TeamCity 2025.11.7 release notes
- JetBrains Blog: TeamCity 2026.1.3 and 2025.11.7 Are Now Available
- TeamCity product page
- CISA advisory AA23-347A on SVR exploitation of TeamCity CVE-2023-42793
- CISA Known Exploited Vulnerabilities Catalog
- CISA KEV catalog search for TeamCity



