TeamCity vulnerabilities and CVEs
Known vulnerabilities affecting TeamCity, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.
22 vulnerabilities tracked. 1 confirmed exploited in the wild. 1 with public exploit code.
- — JetBrains TeamCity Deserialization of Untrusted Data Vulnerability
- 9.9 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings
- 9.9 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection
- 9.9 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings
- 9.9 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings
- 8.8 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the pipeline YAML file path
- 8.8 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the external artifact cache
- 8.1 In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Disk Usage and Build Time pages was possible
- 7.7 In JetBrains TeamCity before 2026.1.3, 2025.11.7 xXE via Maven settings file upload was possible
- 7.7 In JetBrains TeamCity before 2026.1.3, 2025.11.8 disclosure of password parameter values to project viewers was possible
- 7.6 In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Docker Container Info tab was possible
- 7.6 In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Promote build dialog was possible
- 7.6 In JetBrains TeamCity before 2026.1.3, 2025.11.7 missing authorization in the Kubernetes integration allowed project viewers to use stored…
- 7.5 In JetBrains TeamCity before 2026.1.3, 2025.11.7 DoS via agent command results was possible
- 7.3 In JetBrains TeamCity before 2026.1.3, 2025.11.7 xXE in the .NET build steps auto-discovery was possible
- 7.2 In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in project import archives
- 6.6 In JetBrains TeamCity before 2026.1.3, 2025.11.7 privilege escalation to system administrator was possible after disabling per-project…
- 5.4 In JetBrains TeamCity before 2026.1.3 improper authorization allowed project viewers to change project IDs
- 4.8 In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Shared Resources build feature was possible
- 4.3 In JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces
- 3.1 In JetBrains TeamCity before 2026.1.3 privilege escalation was possible by issuing new tokens from a restricted access token
- 3.1 In JetBrains TeamCity before 2026.1.3 privilege escalation was possible via Basic authentication with a restricted access token
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that TeamCity is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other products tracked here
Linux Windows Server 2025 Windows Server 2025 (Server Core installation) Windows 11 version 26H1 Windows 11 Version 24H2 Windows 11 Version 25H2 Windows Server 2022 Windows Server 2019 Windows Server 2019 (Server Core installation) Windows 10 Version 21H2 Windows 10 Version 22H2 Windows 10 Version 1809 Windows 11 Version 23H2 Windows Server 2016 Windows Server 2016 (Server Core installation) Windows 10 Version 1607 Red Hat Enterprise Linux 9 Windows 11 Version 26H2 Red Hat Enterprise Linux 8 Windows Server 2012 R2 (Server Core installation) Windows Server 2012 R2 Chrome Windows Server 2012 (Server Core installation) Windows Server 2012