JetBrains TeamCity Deserialization of Untrusted Data Vulnerability

JetBrains TeamCity Authentication Bypass Vulnerability

JetBrains TeamCity Authentication Bypass Vulnerability

JetBrains TeamCity Relative Path Traversal Vulnerability

In JetBrains TeamCity before 2026.1.3 2025.11.7 kotlin DSL sandbox escape leading to RCE on the server was possible

In JetBrains TeamCity before 2026.1.2, 2025.11.6 сode execution via Kotlin DSL sandbox escape was possible

In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution via a whitelist bypass in the build messages protocol was possible

In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 administrator account takeover was possible via password reset

In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions

In JetBrains TeamCity before 2025.03.1 improper path validation in loggingPreset parameter was possible

In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration

In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases

In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible

In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible

In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents

JetBrains TeamCity before 2021.2.3 was vulnerable to OS command injection in the Agent Push feature configuration

In JetBrains TeamCity before 2021.2.1, XXE during the parsing of the configuration file was possible

In JetBrains TeamCity before 2021.1.4, GitLab authentication impersonation was possible

In JetBrains TeamCity before 2021.1.3, the X-Frame-Options header is missing in some cases

In JetBrains TeamCity before 2021.1.2, permission checks in the Agent Push functionality were insufficient

In JetBrains TeamCity before 2021.1.2, remote code execution via the agent push functionality is possible

In JetBrains TeamCity before 2020.2.4, there was an insecure deserialization

In JetBrains TeamCity before 2020.2.4, OS command injection leading to remote code execution was possible

In JetBrains TeamCity before 2020.2.4 on Windows, arbitrary code execution on TeamCity Server was possible

In JetBrains TeamCity before 2020.2.3, argument injection leading to remote code execution was possible

In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution

In JetBrains UpSource versions before 2018.2 build 1293, there is credential disclosure via RPC commands

An issue was discovered in JetBrains TeamCity 2018.2.4

In JetBrains TeamCity before 2025.07 path traversal was possible via plugin unpacking on Windows

In JetBrains TeamCity before 2026.1.2, 2025.11.6 code execution in Git VCS roots was possible

In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources

In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 authenticated users could execute commands on Windows servers via CRLF injection in Pipeline Git connection settings

In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possible via the versioned settings Kotlin DSL

In JetBrains TeamCity before 2026.1.2 arbitrary file access was possible via the Perforce VCS integration

In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings

In JetBrains TeamCity before 2025.07 a CSRF was possible on GraphQL endpoint

In JetBrains TeamCity before 2025.07 a CSRF was possible in GitHub App connection flow

In JetBrains TeamCity before 2024.12 access tokens were not revoked after removing user roles

In JetBrains TeamCity before 2023.11.1 a CSRF on login was possible

In JetBrains TeamCity before 2023.05.2 a token with limited permissions could be used to gain full account access

In JetBrains TeamCity before 2022.04.2 build parameter injection was possible

In JetBrains TeamCity before 2021.2.1, URL injection leading to CSRF was possible

In JetBrains TeamCity before 2020.2.3, account takeover was potentially possible during a password reset

In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges

In JetBrains TeamCity before 2026.1.1 reflected XSS in the keyword filter was possible

In JetBrains TeamCity before 2026.1.2 pipeline modification was possible due to improper permission checks

In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions

In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions

In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 a third-party agent could impersonate a cloud agent

In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector