JetBrains released TeamCity On-Premises versions 2026.1.3 and 2025.11.8 on November 18, resolving 21 vulnerabilities in the CI/CD server. The most severe, CVE-2026-132231, carries a CVSS score of 9.9 and lets a low-privileged user achieve remote code execution on Windows hosts.
Twenty-One Fixes From Critical RCE to Low-Severity Privilege Escalation
The update spans the severity scale, from the critical remote code execution flaw down to a low-severity privilege escalation bug. JetBrains confirmed that none of the vulnerabilities have been exploited in the wild and that no public exploit code exists for them.
CVE-2026-132231 and Best-Fit Character Mapping in Perforce Settings
CVE-2026-132231 stems from best-fit character mapping in TeamCity’s Perforce settings. A user with low privileges can use it to run code on a TeamCity server that runs on Windows. The requirement for only low privileges widens the set of people who could trigger it, since the account needed to attempt the attack is far less powerful than an administrator’s.
Argument Injection in Perforce and Mercurial VCS Roots
CVE-2026-132232 and CVE-2026-132234 allow command execution through argument injection in the settings for Perforce and Mercurial version-control roots. Both flaws sit in the configuration that tells TeamCity how to connect to a source repository.
Build Attribute Injection and Project Import Path Traversal
CVE-2026-132233 is a build attribute injection flaw, and CVE-2026-132235 is a path traversal flaw in project import archives. Each provides an additional route to remote code execution, which brings to five the number of named CVEs that JetBrains’s update ties to code execution paths.
All five code-execution flaws sit in features that connect TeamCity to outside systems or import outside content: Perforce and Mercurial roots, build attributes and project archives.
Why a TeamCity Build Server Is a High-Value Target
A CI/CD server such as TeamCity holds source repositories, production credentials and deployment pipelines. A compromise therefore reaches beyond the server itself: an attacker who controls a build system can read proprietary code, collect secrets stored for deployments and potentially alter what the pipeline ships to production.
That position makes build servers a recurring supply-chain target.
How the Low-Privilege Requirement Changes the Risk
Many of the flaws can be reached from inside TeamCity’s configuration features rather than from an unauthenticated network request. In an organization where many developers hold accounts, a flaw that needs only a low-privileged login is within reach of any user with such an account, and of any attacker who obtains one through phishing or credential theft.
The settings involved, Perforce and Mercurial roots and project imports, are features that development teams use routinely, so the vulnerable paths are not obscure.
TeamCity 2026.1.3 and 2025.11.8 Upgrade Paths
CVE-2026-132231 is the only flaw in the update rated 9.9, and JetBrains describes it as exploitable on Windows hosts. The company shipped fixes on two lines, 2026.1.3 and 2025.11.8, so organizations on either branch have a patched build available. The advisories range from that critical remote code execution bug down to a low-severity privilege escalation, so administrators should not stop reading at the headline score.
The fixed versions are 2026.1.3 and 2025.11.8. JetBrains has not reported attacks, and the absence of public exploit code gives administrators time, though the specific descriptions of the flaws, including the Perforce character mapping detail, give researchers a starting point for building their own proofs of concept.
Organizations running TeamCity on Windows hosts have the most direct exposure to the 9.9-rated flaw, and the update is the only remediation JetBrains describes. The remaining 16 fixes in the release, which range down to a low-severity privilege escalation, are not itemized in the vendor information available, so the full risk picture for the update will emerge as JetBrains and outside researchers publish more detail.
