In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths
Search vulnerabilities
In JetBrains TeamCity before 2026.2.1 remote code execution was possible via the Notification Rules form
In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected credentials
In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible
In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible
In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the thread dump page was possible
In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud profiles
In JetBrains TeamCity before 2026.2.1 arbitrary file read was possible via symlinks in Mercurial subrepositories
In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible
In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via local repository URLs in Subversion VCS roots
In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL settings
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings
In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possible
In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible
In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed queuing builds with personal changes of other users
In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable