# CISA Warns of Ransomware Exploiting TeamCity Vulnerability

- **Canonical URL:** https://www.probackend.com/active-vulnerability-exploitation/cisa-warns-of-ransomware-exploiting-teamcity-vulnerability
- **Section:** Vulnerabilities & Exploits
- **Published:** 2026-11-19
- **Summary:** CISA lists a TeamCity flaw amid ransomware exploitation reports. Review fixed versions, mitigations, and indicators for self-managed servers.

---

## CISA Warns of Ransomware Exploitation of TeamCity Vulnerability

CISA added CVE-2026-63077 to its Known Exploited Vulnerabilities (KEV) catalog, and reporting on the alert says ransomware actors are exploiting the flaw. JetBrains says it has received reports of successful and attempted exploitation against unpatched servers. Those reports establish activity in the wild, not that every vulnerable server was compromised. ([CISA KEV catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog); [BleepingComputer reporting](https://www.bleepingcomputer.com/news/security/cisa-ransomware-gangs-now-exploiting-critical-teamcity-flaw/); [JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

JetBrains describes CVE-2026-63077 as an unauthenticated remote code execution vulnerability. An attacker who can reach a vulnerable TeamCity server over HTTP(S) can exploit its agent polling protocol to run operating-system commands with the privileges of the TeamCity server process. Depending on those privileges and the server’s access, a successful intrusion could expose data, configurations, or stored credentials; alter server state; or affect build artifacts and downstream pipelines. ([JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

TeamCity supports software build, test, and deployment workflows, so a server compromise can reach beyond the application itself. Administrators of self-managed instances should identify exposed servers, mitigate the vulnerability, and investigate the vendor’s indicators. Exploitation reports do not establish compromise of a particular server, and log entries or unfamiliar agents are leads to investigate—not proof on their own. ([JetBrains TeamCity documentation](https://www.jetbrains.com/help/teamcity/teamcity-documentation.html); [JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/); [Securing On-Premises CI/CD](https://spendlens.com/articles/critical-teamcity-cve-2026-63077-vulnerability-sparks-immediate-patch-warnings-f))

## Apply the fix or restrict access

JetBrains identifies TeamCity 2025.11.7 and 2026.1.3 as fixed releases. Upgrade to one of these versions following the vendor’s instructions. If an immediate upgrade is not possible, JetBrains offers a security patch plugin for TeamCity 2017.1 and later. The plugin addresses this vulnerability; JetBrains recommends upgrading to the latest version to receive other security fixes. ([JetBrains advisory and update guidance](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

If an internet-accessible server cannot be upgraded or patched immediately, temporarily restrict external access until mitigation is in place. For ongoing protection, JetBrains recommends limiting access to trusted networks; using a VPN or an additional security layer for internet-facing servers; running TeamCity with only the operating-system privileges it needs; and placing the server on dedicated hosts separate from build agents. These controls reduce exposure but do not replace the fixed release or plugin. ([JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

JetBrains says TeamCity Cloud customers do not need to take action because the necessary mitigations have already been applied. This does not cover self-managed deployments, whose administrators should assess and secure their own instances. ([JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

## Investigate the vendor’s indicators

After mitigation, review TeamCity server logs for `com.thoughtworks.xstream.converters.ConversionException`. JetBrains says this may indicate an exploit attempt or successful exploitation and warrants further investigation; the message alone does not determine which occurred.

On servers already upgraded or protected by the security patch plugin, also look for `com.thoughtworks.xstream.security.ForbiddenClassException`. JetBrains says this can indicate an exploit attempt after patching and, in that case, that the patch or fixed version blocked it. ([JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

Check the unauthorized build-agent list for unexpected entries, particularly agents whose names begin with `scan`. JetBrains says these may indicate an attempted exploit against a server whose URL was reachable by an attacker and can be safely removed. Use timestamps from relevant log messages—not the date displayed for an unauthorized agent, to assess timing. Preserve relevant records, correlate the evidence, and contact TeamCity Support if you need help interpreting it. If the investigation finds evidence of broader access, assess the data, configurations, credentials, server state, and build integrity the server could affect. ([JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

For exposed self-managed TeamCity servers, the response is to restrict access if immediate mitigation is not possible, install a fixed release or the applicable security plugin, and review the vendor’s log and agent indicators. CISA’s listing and the reported exploitation make timely action important; the findings of an investigation should still be based on evidence from the affected server. ([CISA KEV catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog); [BleepingComputer reporting](https://www.bleepingcomputer.com/news/security/cisa-ransomware-gangs-now-exploiting-critical-teamcity-flaw/); [JetBrains advisory](https://blog.jetbrains.com/teamcity/2026/08/cve-2026-63077-update/))

![cisa warns of ransomware exploitation of teamcity vulnerability](https://assets.probackend.com/eb307c41-486e-42e2-bfa6-d6ad33b8ac39?token=ast_7b9ee8975a4b187969d396286e3f9717c42f2331)

![cisa warns of ransomware exploitation of teamcity vulnerability](https://assets.probackend.com/a4165add-1879-434c-89ae-2c3c01b34574?token=ast_7b9ee8975a4b187969d396286e3f9717c42f2331)
