CVE-2026-132231 Security Alert: CRITICAL Vulnerability
Urgent: CVE-2026-132231 requires immediate attention.
· 7 min read
Executive Summary
CVE-2026-132231 is a critical remote code execution vulnerability in JetBrains TeamCity, with a CVSS score of 9.9. The issue affects TeamCity before 2026.1.3 and 2025.11.7, where remote code execution was possible through best-fit character mapping in Perforce settings. Even though there is no known exploitation in the wild and it is not in CISA KEV, the severity means solo developers and small teams should treat this as an urgent patch-and-verify event.
If you run TeamCity on a public-facing server, assume the blast radius includes build secrets, source code, CI credentials, and the ability to modify pipelines or deploy malicious artifacts. Patch immediately, isolate the service until updated, and review any Perforce-related configuration.
Immediate Action
- Upgrade TeamCity immediately to a fixed release:
2026.1.3+or the vendor’s latest patched build. If you cannot patch today, take TeamCity offline or restrict access to trusted VPN/IPs only. - Disable or remove Perforce integrations until the upgrade is complete, especially any configuration that uses character mapping or non-ASCII path handling.
- Isolate the TeamCity server from the internet and from production credentials. Rotate any tokens, SSH keys, and service accounts that TeamCity can access.
- Check recent build activity for unexpected changes, new build steps, altered agents, or unknown artifacts. Treat suspicious pipeline edits as possible compromise.
- Back up configuration and logs before making changes, then patch and restart the service. If patching fails, roll back to a known-good snapshot only after confirming the snapshot predates exposure.
- Review vendor guidance at JetBrains TeamCity security advisory and apply any additional hardening steps listed there.
Affected Versions
JetBrains TeamCity < 2026.1.3vulnerableJetBrains TeamCity 2025.11.7vulnerableJetBrains TeamCity 2026.1.3+safe, per current advisoryJetBrains TeamCity latest patched releasepreferred if available
Note: If you run TeamCity in Docker, Kubernetes, or behind a reverse proxy, the vulnerable version is still vulnerable regardless of deployment method.
Resolution Guide
TeamCity patching: update the server package or container image to the fixed release. Use the vendor’s installer or image tag that contains 2026.1.3+.
# Linux package install example (replace with your distro/package name)
sudo systemctl stop teamcity
sudo apt-get update
sudo apt-get install --only-upgrade teamcity-server
sudo systemctl start teamcity
# If using yum/dnf
sudo systemctl stop teamcity
sudo yum update teamcity-server
sudo systemctl start teamcity
# Docker example: replace TODO tag with the patched TeamCity image
docker pull jetbrains/teamcity-server:TODO-patched-tag
docker stop teamcity
docker rm teamcity
docker run -d --name teamcity \
-p 8111:8111 \
-v teamcity_data:/data/teamcity_server/datadir \
jetbrains/teamcity-server:TODO-patched-tag
Config hardening:
# Example: temporarily disable Perforce integration in TeamCity settings
# TODO: exact UI path depends on your setup
# Remove or disable Perforce VCS roots and any character-mapping options
Java build/dependency ecosystems: this issue is in the TeamCity server, not a library you upgrade via npm/pip/Maven. Still, if your automation scripts pin TeamCity-related tooling or plugins, update them too.
# npm/yarn/pnpm: check scripts or wrappers that talk to TeamCity
npm audit --production
yarn audit
pnpm audit
# Python
pip list | grep -i teamcity
pipx list
# Maven/Gradle: inspect build scripts for TeamCity plugin references
grep -Rni "teamcity" .
./mvnw -q dependency:tree | grep -i teamcity || true
./gradlew dependencies | grep -i teamcity || true
Minimal hardening example: if you have automation that provisions TeamCity, add a guard to block startup on vulnerable versions.
# Example shell guard
VERSION="$(teamcity-server --version 2>/dev/null || true)"
case "$VERSION" in
*2026.1.3*|*2026.1.4*|*2026.1.5*) echo "OK";;
*) echo "Refusing to start vulnerable TeamCity version: $VERSION"; exit 1;;
esac
Detection & Verification
Check the installed version:
# Linux service/package
teamcity-server --version 2>/dev/null || true
rpm -qa | grep -i teamcity || true
dpkg -l | grep -i teamcity || true
# Docker
docker inspect --format '{{.Config.Image}}' teamcity
docker images | grep -i teamcity
Look for Perforce-related configuration:
grep -RniE "perforce|p4|character mapping|best-fit" /opt/teamcity /data/teamcity_server/datadir 2>/dev/null
Verify the fix:
# Confirm the server reports a fixed version
teamcity-server --version
# Confirm service is running and reachable only where intended
sudo systemctl status teamcity
curl -fsS http://127.0.0.1:8111/login.html | head
# Re-run dependency/config scans after upgrade
grep -RniE "perforce|p4|character mapping|best-fit" /opt/teamcity /data/teamcity_server/datadir 2>/dev/null
If you use a vulnerability scanner, rescan the host and container image after patching. Also review logs for unexpected admin actions, new build agents, or pipeline edits during the exposure window.
Risk and Impact
This flaw can allow an attacker to execute arbitrary code on the TeamCity server, which may lead to full compromise of your CI/CD environment. For a solo developer or small team, that can mean stolen source code, leaked API keys, tampered builds, and malicious releases pushed to customers.
The most serious risk is supply-chain impact: once an attacker controls TeamCity, they may be able to alter build outputs or inject backdoors into software you ship. Even without known active exploitation, the severity and placement of TeamCity in the delivery pipeline make this a high-priority incident response item.