Jetbrains Teamcity — known CVE vulnerabilities

Every CVE whose affected-product data names Jetbrains Teamcity, ordered by CVSS severity, with EPSS exploit prediction and CISA KEV status.

CVEs (200)

• CVE-2021-43193 — CVSS 9.8 (critical): In JetBrains TeamCity before 2021.1.2, remote code execution via the agent push functionality is possible.
• CVE-2024-23917 — CVSS 9.8 (critical): In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible
• CVE-2021-31909 — CVSS 9.8 (critical): In JetBrains TeamCity before 2020.2.3, argument injection leading to remote code execution was possible.
• CVE-2021-37544 — CVSS 9.8 (critical): In JetBrains TeamCity before 2020.2.4, there was an insecure deserialization.
• CVE-2021-31914 — CVSS 9.8 (critical): In JetBrains TeamCity before 2020.2.4 on Windows, arbitrary code execution on TeamCity Server was possible.
• CVE-2024-27198 — CVSS 9.8 (critical) — actively exploited: In JetBrains TeamCity before 2023.11.4 authentication bypass allowing to perform admin actions was possible
• CVE-2022-25263 — CVSS 9.8 (critical): JetBrains TeamCity before 2021.2.3 was vulnerable to OS command injection in the Agent Push feature configuration.
• CVE-2019-12157 — CVSS 9.8 (critical): In JetBrains UpSource versions before 2018.2 build 1293, there is credential disclosure via RPC commands.
• CVE-2022-24340 — CVSS 9.8 (critical): In JetBrains TeamCity before 2021.2.1, XXE during the parsing of the configuration file was possible.
• CVE-2019-18364 — CVSS 9.8 (critical): In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution.
• CVE-2021-31915 — CVSS 9.8 (critical): In JetBrains TeamCity before 2020.2.4, OS command injection leading to remote code execution was possible.
• CVE-2022-24331 — CVSS 9.8 (critical): In JetBrains TeamCity before 2021.1.4, GitLab authentication impersonation was possible.
• CVE-2021-43202 — CVSS 9.8 (critical): In JetBrains TeamCity before 2021.1.3, the X-Frame-Options header is missing in some cases.
• CVE-2021-43200 — CVSS 9.8 (critical): In JetBrains TeamCity before 2021.1.2, permission checks in the Agent Push functionality were insufficient.
• CVE-2019-15039 — CVSS 9.8 (critical): An issue was discovered in JetBrains TeamCity 2018.2.4. It had a possible remote code execution issue. This was fixed in TeamCity 2019.1.
• CVE-2023-42793 — CVSS 9.8 (critical) — actively exploited: In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible
• CVE-2023-34218 — CVSS 9.1 (critical): In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible
• CVE-2020-15825 — CVSS 8.8 (high): In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.
• CVE-2022-24342 — CVSS 8.8 (high): In JetBrains TeamCity before 2021.2.1, URL injection leading to CSRF was possible.
• CVE-2021-31912 — CVSS 8.8 (high): In JetBrains TeamCity before 2020.2.3, account takeover was potentially possible during a password reset.
• CVE-2026-44413 — CVSS 8.2 (high): In JetBrains TeamCity before 2026.1 2025.11.5 authenticated users could expose server API to unauthorised access
• CVE-2024-36470 — CVSS 8.1 (high): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases
• CVE-2022-24335 — CVSS 8.1 (high): JetBrains TeamCity before 2021.2 was vulnerable to a Time-of-check/Time-of-use (TOCTOU) race-condition attack in agent registration via…
• CVE-2025-54531 — CVSS 7.7 (high): In JetBrains TeamCity before 2025.07 path traversal was possible via plugin unpacking on Windows
• CVE-2025-26492 — CVSS 7.7 (high): In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources
• CVE-2025-59457 — CVSS 7.7 (high): In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on Windows
• CVE-2026-49374 — CVSS 7.6 (high): In JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parameters
• CVE-2021-37545 — CVSS 7.5 (high): In JetBrains TeamCity before 2021.1.1, insufficient authentication checks for agent requests were made.
• CVE-2021-25776 — CVSS 7.5 (high): In JetBrains TeamCity before 2020.2, an ECR token could be exposed in a build's parameters.
• CVE-2022-25264 — CVSS 7.5 (high): In JetBrains TeamCity before 2021.2.3, environment variables of the "password" type could be logged in some cases.
• CVE-2022-24341 — CVSS 7.5 (high): In JetBrains TeamCity before 2021.2.1, editing a user account to change its password didn't terminate sessions of the edited user.
• CVE-2021-26310 — CVSS 7.5 (high): In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible.
• CVE-2021-37548 — CVSS 7.5 (high): In JetBrains TeamCity before 2021.1, passwords in cleartext sometimes could be stored in VCS.
• CVE-2020-11688 — CVSS 7.5 (high): In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session.
• CVE-2024-43114 — CVSS 7.5 (high): In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions
• CVE-2020-11687 — CVSS 7.5 (high): In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages.
• CVE-2021-31910 — CVSS 7.5 (high): In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible.
• CVE-2021-31913 — CVSS 7.5 (high): In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange.
• CVE-2019-12841 — CVSS 7.5 (high): Incorrect handling of user input in ZIP extraction was detected in JetBrains TeamCity. The issue was fixed in TeamCity 2018.2.2.
• CVE-2026-49372 — CVSS 7.5 (high): In JetBrains TeamCity before 2026.1, 2025.11.5 unauthenticated SSRF via build status was possible
• CVE-2025-54530 — CVSS 7.5 (high): In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions
• CVE-2020-35667 — CVSS 7.5 (high): JetBrains TeamCity Plugin before 2020.2.85695 SSRF. Vulnerability that could potentially expose user credentials.
• CVE-2020-7909 — CVSS 7.5 (high): In JetBrains TeamCity before 2019.1.5, some server-stored passwords could be shown via the web UI.
• CVE-2025-57732 — CVSS 7.5 (high): In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership
• CVE-2019-15042 — CVSS 7.5 (high): An issue was discovered in JetBrains TeamCity 2018.2.4. It had no SSL certificate validation for some external https connections. This was…
• CVE-2021-43196 — CVSS 7.5 (high): In JetBrains TeamCity before 2021.1, information disclosure via the Docker Registry connection dialog is possible.
• CVE-2019-15038 — CVSS 7.5 (high): An issue was discovered in JetBrains TeamCity 2018.2.4. The TeamCity server was not using some security-related HTTP headers. The issue was…
• CVE-2024-41827 — CVSS 7.4 (high): In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration
• CVE-2024-31136 — CVSS 7.4 (high): In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter
• CVE-2024-27199 — CVSS 7.3 (high) — actively exploited: In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible
• CVE-2019-15036 — CVSS 7.2 (high): An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could execute any command on the server machine…
• CVE-2026-49373 — CVSS 7.1 (high): In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings
• CVE-2026-49371 — CVSS 7.1 (high): In JetBrains TeamCity before 2026.1.1 reflected XSS in the keyword filter was possible
• CVE-2024-31137 — CVSS 6.8 (medium): In JetBrains TeamCity before 2024.03 reflected XSS was possible via Space connection configuration
• CVE-2024-36365 — CVSS 6.8 (medium): 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
• CVE-2022-46831 — CVSS 6.6 (medium): In JetBrains TeamCity between 2022.10 and 2022.10.1 connecting to AWS using the "Default Credential Provider Chain" allowed TeamCity…
• CVE-2025-68267 — CVSS 6.5 (medium): In JetBrains TeamCity before 2025.11.1 excessive privileges were possible due to storing GitHub personal access token instead of an…
• CVE-2020-15828 — CVSS 6.5 (medium): In JetBrains TeamCity before 2020.1.1, project parameter values can be retrieved by a user without appropriate permissions.
• CVE-2020-11689 — CVSS 6.5 (medium): In JetBrains TeamCity before 2019.2.1, a user without appropriate permissions was able to import settings from the settings.kts file.
• CVE-2024-36377 — CVSS 6.5 (medium): In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions
• CVE-2026-49379 — CVSS 6.5 (medium): In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names
• CVE-2026-49376 — CVSS 6.5 (medium): In JetBrains TeamCity before 2026.1 insufficient username validation in the SAML plugin
• CVE-2024-31134 — CVSS 6.5 (medium): In JetBrains TeamCity before 2024.03 authenticated users without administrative permissions could register other users when…
• CVE-2024-36376 — CVSS 6.5 (medium): In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions
• CVE-2022-24333 — CVSS 6.5 (medium): In JetBrains TeamCity before 2021.2, blind SSRF via an XML-RPC call was possible.
• CVE-2015-1313 — CVSS 6.5 (medium): JetBrains TeamCity 8 and 9 before 9.0.2 allows bypass of account-creation restrictions via a crafted request because the required request…
• CVE-2025-24461 — CVSS 6.5 (medium): In JetBrains TeamCity before 2024.12.1 decryption of connection secrets without proper permissions was possible via Test Connection endpoint
• CVE-2022-24337 — CVSS 6.5 (medium): In JetBrains TeamCity before 2021.2, health items of pull requests were shown to users who lacked appropriate permissions.
• CVE-2022-44624 — CVSS 6.5 (medium): In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters
• CVE-2024-36362 — CVSS 6.5 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 path traversal allowing to read files from server was…
• CVE-2024-36364 — CVSS 6.5 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 improper access control in Pull Requests and Commit status…
• CVE-2022-44623 — CVSS 6.5 (medium): In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings
• CVE-2024-41824 — CVSS 6.4 (medium): In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases
• CVE-2024-56351 — CVSS 6.3 (medium): In JetBrains TeamCity before 2024.12 access tokens were not revoked after removing user roles
• CVE-2024-31135 — CVSS 6.1 (medium): In JetBrains TeamCity before 2024.03 open redirect was possible on the login page
• CVE-2019-12844 — CVSS 6.1 (medium): A possible stored JavaScript injection was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2.3.
• CVE-2020-7911 — CVSS 6.1 (medium): In JetBrains TeamCity before 2019.2, several user-level pages were vulnerable to XSS.
• CVE-2022-24330 — CVSS 6.1 (medium): In JetBrains TeamCity before 2021.2.1, a redirection to an external site was possible.
• CVE-2019-15848 — CVSS 6.1 (medium): JetBrains TeamCity 2019.1 and 2019.1.1 allows cross-site scripting (XSS), potentially making it possible to send an arbitrary HTTP request…
• CVE-2019-12842 — CVSS 6.1 (medium): A reflected XSS on a user page was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2.2.
• CVE-2020-15831 — CVSS 6.1 (medium): JetBrains TeamCity before 2019.2.3 is vulnerable to reflected XSS in the administration UI.
• CVE-2020-15830 — CVSS 6.1 (medium): JetBrains TeamCity before 2019.2.3 is vulnerable to stored XSS in the administration UI.
• CVE-2019-12843 — CVSS 6.1 (medium): A possible stored JavaScript injection requiring a deliberate server administrator action was detected. The issue was fixed in JetBrains…
• CVE-2022-25261 — CVSS 6.1 (medium): JetBrains TeamCity before 2021.2.2 was vulnerable to reflected XSS.
• CVE-2021-37542 — CVSS 6.1 (medium): In JetBrains TeamCity before 2020.2.3, XSS was possible.
• CVE-2021-25773 — CVSS 6.1 (medium): JetBrains TeamCity before 2020.2 was vulnerable to reflected XSS on several pages.
• CVE-2020-27627 — CVSS 6.1 (medium): JetBrains TeamCity before 2020.1.2 was vulnerable to URL injection.
• CVE-2022-24338 — CVSS 6.1 (medium): JetBrains TeamCity before 2021.2.1 was vulnerable to reflected XSS.
• CVE-2019-15037 — CVSS 6.1 (medium): An issue was discovered in JetBrains TeamCity 2018.2.4. It had several XSS vulnerabilities on the settings pages. The issues were fixed in…
• CVE-2021-43197 — CVSS 6.1 (medium): In JetBrains TeamCity before 2021.1.2, email notifications could include unescaped HTML for XSS.
• CVE-2021-31911 — CVSS 6.1 (medium): In JetBrains TeamCity before 2020.2.3, reflected XSS was possible on several pages.
• CVE-2026-49375 — CVSS 6.1 (medium): In JetBrains TeamCity before 2026.1, 2025.11.5 reflected XSS was possible on the repository download page
• CVE-2021-31904 — CVSS 6.1 (medium): In JetBrains TeamCity before 2020.2.2, XSS was potentially possible on the test history page.
• CVE-2024-31139 — CVSS 5.9 (medium): In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector
• CVE-2024-56356 — CVSS 5.9 (medium): In JetBrains TeamCity before 2024.12 insecure XMLParser configuration could lead to potential XXE attack
• CVE-2024-36378 — CVSS 5.9 (medium): In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens
• CVE-2024-28174 — CVSS 5.8 (medium): In JetBrains TeamCity before 2023.11.4 presigned URL generation requests in S3 Artifact Storage plugin were authorized improperly
• CVE-2025-54535 — CVSS 5.8 (medium): In JetBrains TeamCity before 2025.07 password reset and email verification tokens were using weak hashing algorithms
• CVE-2024-56353 — CVSS 5.5 (medium): In JetBrains TeamCity before 2024.12 backup file exposed user credentials and session cookies
• CVE-2025-54538 — CVSS 5.5 (medium): In JetBrains TeamCity before 2025.07 password exposure was possible via command line in the "hg pull" command
• CVE-2024-35301 — CVSS 5.5 (medium): In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token
• CVE-2025-57733 — CVSS 5.5 (medium): In JetBrains TeamCity before 2025.07.1 sMTP injection was possible allowing modification of email content
• CVE-2025-59456 — CVSS 5.5 (medium): In JetBrains TeamCity before 2025.07.2 path traversal was possible during project archive upload
• CVE-2024-56354 — CVSS 5.5 (medium): In JetBrains TeamCity before 2024.12 password field value were accessible to users with view settings permission
• CVE-2025-54537 — CVSS 5.5 (medium): In JetBrains TeamCity before 2025.07 user credentials were stored in plain text in memory snapshots
• CVE-2025-52876 — CVSS 5.4 (medium): In JetBrains TeamCity before 2025.03.3 reflected XSS on the favoriteIcon page was possible
• CVE-2022-48343 — CVSS 5.4 (medium): In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process.
• CVE-2022-48344 — CVSS 5.4 (medium): In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process.
• CVE-2022-36322 — CVSS 5.4 (medium): In JetBrains TeamCity before 2022.04.2 build parameter injection was possible
• CVE-2024-36366 — CVSS 5.4 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 an XSS could be executed via certain report grouping and filtering…
• CVE-2021-43198 — CVSS 5.4 (medium): In JetBrains TeamCity before 2021.1.2, stored XSS is possible.
• CVE-2021-3315 — CVSS 5.4 (medium): In JetBrains TeamCity before 2020.2.2, stored XSS on a tests page was possible.
• CVE-2021-31908 — CVSS 5.4 (medium): In JetBrains TeamCity before 2020.2.3, stored XSS was possible on several pages.
• CVE-2025-68165 — CVSS 5.4 (medium): In JetBrains TeamCity before 2025.11 reflected XSS was possible on VCS Root setup
• CVE-2025-68166 — CVSS 5.4 (medium): In JetBrains TeamCity before 2025.11 a DOM-based XSS was possible on the OAuth connections tab
• CVE-2020-7910 — CVSS 5.4 (medium): JetBrains TeamCity before 2019.2 was vulnerable to a stored XSS attack by a user with the developer role.
• CVE-2025-52875 — CVSS 5.4 (medium): In JetBrains TeamCity before 2025.03.3 a DOM-based XSS at the Performance Monitor page was possible
• CVE-2025-54536 — CVSS 5.4 (medium): In JetBrains TeamCity before 2025.07 a CSRF was possible on GraphQL endpoint
• CVE-2025-68268 — CVSS 5.4 (medium): In JetBrains TeamCity before 2025.11.1 reflected XSS was possible on the storage settings page
• CVE-2024-35302 — CVSS 5.4 (medium): In JetBrains TeamCity before 2023.11 stored XSS during restore from backup was possible
• CVE-2022-24339 — CVSS 5.4 (medium): JetBrains TeamCity before 2021.2.1 was vulnerable to stored XSS.
• CVE-2025-54528 — CVSS 5.4 (medium): In JetBrains TeamCity before 2025.07 a CSRF was possible in GitHub App connection flow
• CVE-2023-39173 — CVSS 5.4 (medium): In JetBrains TeamCity before 2023.05.2 a token with limited permissions could be used to gain full account access
• CVE-2021-37547 — CVSS 5.3 (medium): In JetBrains TeamCity before 2020.2.4, insufficient checks during file uploading were made.
• CVE-2019-12845 — CVSS 5.3 (medium): The generated Kotlin DSL settings allowed usage of an unencrypted connection for resolving artifacts. The issue was fixed in JetBrains…
• CVE-2019-18363 — CVSS 5.3 (medium): In JetBrains TeamCity before 2019.1.2, access could be gained to the history of builds of a deleted build configuration under some…
• CVE-2019-18366 — CVSS 5.3 (medium): In JetBrains TeamCity before 2019.1.2, secure values could be exposed to users with the "View build runtime parameters and data" permission.
• CVE-2019-18367 — CVSS 5.3 (medium): In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissions.
• CVE-2020-15829 — CVSS 5.3 (medium): In JetBrains TeamCity before 2019.2.3, password parameters could be disclosed via build logs.
• CVE-2020-27629 — CVSS 5.3 (medium): In JetBrains TeamCity before 2020.1.5, secure dependency parameters could be not masked in depending builds when there are no internal…
• CVE-2021-25772 — CVSS 5.3 (medium): In JetBrains TeamCity before 2020.2.2, TeamCity server DoS was possible via server integration.
• CVE-2021-25777 — CVSS 5.3 (medium): In JetBrains TeamCity before 2020.2.1, permissions during token removal were checked improperly.
• CVE-2021-25778 — CVSS 5.3 (medium): In JetBrains TeamCity before 2020.2.1, permissions during user deletion were checked improperly.
• CVE-2021-31907 — CVSS 5.3 (medium): In JetBrains TeamCity before 2020.2.2, permission checks for changing TeamCity plugins were implemented improperly.
• CVE-2021-37546 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.1, an insecure key generation mechanism for encrypted properties was used.
• CVE-2021-43194 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.1.2, user enumeration was possible.
• CVE-2021-43195 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.1.2, some HTTP security headers were missing.
• CVE-2021-43199 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.1.2, permission checks in the Create Patch functionality are insufficient.
• CVE-2021-43201 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.1.3, a newly created project could take settings from an already deleted project.
• CVE-2022-24332 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.2, a logout action didn't remove a Remember Me cookie.
• CVE-2022-24334 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.2.1, the Agent Push feature allowed selection of any private key on the server.
• CVE-2022-24336 — CVSS 5.3 (medium): In JetBrains TeamCity before 2021.2.1, an unauthenticated attacker can cancel running builds via an XML-RPC request to the TeamCity server.
• CVE-2023-34227 — CVSS 5.3 (medium): In JetBrains TeamCity before 2023.05 a specific endpoint was vulnerable to brute force attacks
• CVE-2023-34228 — CVSS 5.3 (medium): In JetBrains TeamCity before 2023.05 authentication checks were missing – 2FA was not checked for some sensitive account actions
• CVE-2024-24938 — CVSS 5.3 (medium): In JetBrains TeamCity before 2023.11.2 limited directory traversal was possible in the Kotlin DSL documentation
• CVE-2024-24942 — CVSS 5.3 (medium): In JetBrains TeamCity before 2023.11.3 path traversal allowed reading data within JAR archives
• CVE-2024-36375 — CVSS 5.3 (medium): In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed
• CVE-2024-56349 — CVSS 5.3 (medium): In JetBrains TeamCity before 2024.12 improper access control allowed unauthorized users to modify build logs
• CVE-2022-48342 — CVSS 5.2 (medium): In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents.
• CVE-2024-39879 — CVSS 5.0 (medium): In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings
• CVE-2014-10002 — CVSS 5.0 (medium): Unspecified vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to obtain sensitive information via unknown vectors.
• CVE-2019-15035 — CVSS 4.9 (medium): An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could get access to potentially confidential…
• CVE-2025-46433 — CVSS 4.9 (medium): In JetBrains TeamCity before 2025.03.1 improper path validation in loggingPreset parameter was possible
• CVE-2020-11938 — CVSS 4.9 (medium): In JetBrains TeamCity 2018.2 through 2019.2.1, a project administrator was able to see scrambled password parameters used in a project. The…
• CVE-2024-47949 — CVSS 4.9 (medium): In JetBrains TeamCity before 2024.07.3 path traversal allowed backup file write to arbitrary location
• CVE-2024-47948 — CVSS 4.9 (medium): In JetBrains TeamCity before 2024.07.3 path traversal leading to information disclosure was possible via server backups
• CVE-2023-34224 — CVSS 4.8 (medium): In JetBrains TeamCity before 2023.05 open redirect during oAuth configuration was possible
• CVE-2025-47852 — CVSS 4.8 (medium): In JetBrains TeamCity before 2025.03.2 stored XSS via YouTrack integration was possible
• CVE-2025-47851 — CVSS 4.8 (medium): In JetBrains TeamCity before 2025.03.2 stored XSS via GitHub Checks Webhook was possible
• CVE-2025-54534 — CVSS 4.8 (medium): In JetBrains TeamCity before 2025.07 reflected XSS was possible on the agentpushPreset page
• CVE-2025-52879 — CVSS 4.8 (medium): In JetBrains TeamCity before 2025.03.3 reflected XSS in the NPM Registry integration was possible
• CVE-2025-52877 — CVSS 4.8 (medium): In JetBrains TeamCity before 2025.03.3 reflected XSS on diskUsageBuildsStats page was possible
• CVE-2025-47853 — CVSS 4.8 (medium): In JetBrains TeamCity before 2025.03.2 stored XSS via Jira integration was possible
• CVE-2024-36373 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible
• CVE-2024-36374 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible
• CVE-2023-38061 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.1 stored XSS when using a custom theme was possible
• CVE-2023-34229 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05 stored XSS in GitLab Connection page was possible
• CVE-2023-34225 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05 stored XSS in the NuGet feed page was possible
• CVE-2024-41825 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab
• CVE-2023-34226 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05 reflected XSS in the Subscriptions page was possible
• CVE-2023-41249 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during copying Build Step
• CVE-2023-41248 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.3 stored XSS was possible during Cloud Profiles configuration
• CVE-2024-31138 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.03 xSS was possible via Agent Distribution settings
• CVE-2023-39175 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.2 reflected XSS via GitHub integration was possible
• CVE-2023-38066 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.1 reflected XSS via the Referer header was possible during artifact downloads
• CVE-2024-36363 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 several Stored XSS in code inspection reports were possible
• CVE-2023-38065 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.1 stored XSS while viewing the build log was possible
• CVE-2023-38063 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.1 stored XSS while running custom builds was possible
• CVE-2024-36367 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible
• CVE-2024-36368 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration was possible
• CVE-2024-36369 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was possible
• CVE-2024-36370 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was possible
• CVE-2024-36371 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible
• CVE-2024-36372 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible
• CVE-2024-43807 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.07.1 multiple stored XSS was possible on Clouds page
• CVE-2024-43810 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.07.1 reflected XSS was possible in the AWS Core plugin
• CVE-2023-34222 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05 possible XSS in the Plugin Vendor URL was possible
• CVE-2024-56352 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.12 stored XSS was possible via image name on the agent details page
• CVE-2023-34221 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05 stored XSS in the Show Connection page was possible
• CVE-2023-34220 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible
• CVE-2024-56355 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.12 missing Content-Type header in RemoteBuildLogController response could lead to XSS
• CVE-2025-24459 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.12.1 reflected XSS was possible on the Vault Connection page
• CVE-2022-48428 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible
• CVE-2022-48427 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible
• CVE-2025-26493 — CVSS 4.6 (medium): In JetBrains TeamCity before 2024.12.2 several DOM-based XSS were possible on the Code Inspection Report tab
• CVE-2025-31140 — CVSS 4.6 (medium): In JetBrains TeamCity before 2025.03 stored XSS was possible on Cloud Profiles page
• CVE-2022-48426 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible
• CVE-2022-29927 — CVSS 4.6 (medium): In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible
• CVE-2025-67741 — CVSS 4.6 (medium): In JetBrains TeamCity before 2025.11 stored XSS was possible via session attribute
• CVE-2024-24937 — CVSS 4.6 (medium): In JetBrains TeamCity before 2023.11.2 stored XSS via agent distribution was possible