Skip to content
Security Alerts

CVE-2026-132231 and 3 More: Remote Code Execution in JetBrains TeamCity

JetBrains fixed four TeamCity flaws that let an authenticated user execute code on the server: via Perforce settings, Mercurial VCS roots and build attributes. Fixed in 2026.1.3 and 2025.11.7...

Summary

ParameterValue
CVE ID (lead entry)CVE-2026-132231
Vulnerabilities covered4 critical (CVE-2026-132231, CVE-2026-132232, CVE-2026-132233, CVE-2026-132234)
Alert SourceGitHub Advisory - Critical Vulnerability
CVE Publication Year2026
Date Published2026-11-18
VendorJetBrains
ProductTeamCity (CI/CD server)
Vulnerability Typeremote code execution (argument injection, best-fit character mapping, build attribute injection)
CVSS Score9.9 (critical)
EPSS ScoreNo data
CISA KEVNo
RansomwareNot confirmed

Vulnerability Description

Source: NVD (CNA: JetBrains)

JetBrains published four vulnerabilities in the TeamCity CI/CD server, each rated 9.9 on the CVSS 3.1 scale. All of them lead to remote code execution on the TeamCity server:

CVEMechanismCWE
CVE-2026-132231best-fit character mapping in Perforce settingsCWE-1289
CVE-2026-132232argument injection in Perforce settingsCWE-88
CVE-2026-132233build attribute injectionCWE-23
CVE-2026-132234argument injection in Mercurial VCS root settingsCWE-88

The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C) means that a low-privileged TeamCity account is enough to attack, and the impact extends beyond the vulnerable component. A CI/CD server stores credentials for code repositories, artifact registries and target environments, so its compromise opens the way to a software supply chain attack. The vendor does not report exploitation in the wild; the flaws are not in the CISA KEV catalog.

Required Actions

  1. Update TeamCity to 2026.1.3 or — on the 2025.11 branch — to 2025.11.7 (according to NVD, earlier versions are affected).
  2. Review TeamCity accounts and permissions: remove unused accounts and limit who can edit project settings and VCS roots.
  3. Do not expose the TeamCity interface to the internet; restrict access to VPN or trusted networks.
  4. After updating, review Perforce and Mercurial VCS root configuration and the project settings change history for unexpected modifications. If you suspect abuse, rotate secrets stored in TeamCity.

Who Is Affected?

Organizations running their own JetBrains TeamCity server (on-premises) in versions before 2026.1.3 and 2025.11.7. The risk is highest where many users or contractors have TeamCity access and the server holds production deployment permissions.

Sources


Need help securing your systems? nFlo team offers vulnerability management and 24/7 SOC services. Contact us.

Learn More

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Grzegorz Gnych

Grzegorz Gnych

Sales Representative

Response within 24 hours
Expert consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations