Threat advisory: JetBrains TeamCity remote code execution, CVE-2026-132891

Published 20 November 2026, 9 pages, Mitigata Threat Research

In plain words

A popular tool that builds and checks software has a serious flaw. An outsider who sends a request to add code can make the tool run their own commands, so the company should update it and limit which outside requests get built.

For business leaders

A critical flaw in JetBrains TeamCity, a build server, lets an outside contributor run code on the server by opening a pull request. The server usually holds source code, deployment credentials and signing keys, so a compromise can reach what a company ships to customers. The advisory rates it 9.8 out of 10 under CVSS 3.1, and CISA records no known exploitation. Upgrading to 2025.11.8, 2026.1.4 or 2026.2 is the only fix JetBrains publishes. Leaders should ask three things: which TeamCity servers exist, including those other teams run, which versions they run, and whether outside pull requests are built without approval. Any suspected compromise must be reported to CERT-In within 6 hours.

For security analysts

CVE-2026-132891, remote code execution via external pull requests in JetBrains TeamCity, classed CWE-696. CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), from the JetBrains CNA; no CVSS 4.0 score; NVD analysis not complete at fetch. Affected: on-premises releases before 2025.11.8 and 2026.1.x before 2026.1.4. Fixed in 2025.11.8, 2026.1.4 and 2026.2. TeamCity Cloud is vendor-patched. Exploitation: CISA SSVC records none known, not automatable; no public exploit listed. No vendor workaround. Steps: 1) inventory servers and versions in web UI footer or Administration; 2) upgrade, exposed servers first; 3) require trusted approval before building outside PRs (interim analysis, not a fix); 4) review PR build steps, spawned processes, outbound connections, and new or modified admin users and tokens. If compromised: treat as full server compromise, isolate, rotate all held secrets, rebuild agents, check artifacts. Mechanism not detailed in sources. Official indicators not published. New versus known: not stated.

Key points

CVE ids covered: CVE-2026-132891

The full report is a PDF that opens with a work email.