Teamcity
by Jetbrains
Source repositories
CVEs (487)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-57732 | Hig | 0.49 | 7.5 | 0.00 | Aug 20, 2025 | In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership | ||
| CVE-2025-54530 | Hig | 0.49 | 7.5 | 0.00 | Jul 28, 2025 | In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions | ||
| CVE-2024-43114 | Hig | 0.49 | 7.5 | 0.00 | Aug 6, 2024 | In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions | ||
| CVE-2022-25264 | Hig | 0.49 | 7.5 | 0.01 | Feb 25, 2022 | In JetBrains TeamCity before 2021.2.3, environment variables of the "password" type could be logged in some cases. | ||
| CVE-2022-24341 | Hig | 0.49 | 7.5 | 0.01 | Feb 25, 2022 | 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-43196 | Hig | 0.49 | 7.5 | 0.01 | Nov 9, 2021 | In JetBrains TeamCity before 2021.1, information disclosure via the Docker Registry connection dialog is possible. | ||
| CVE-2021-37548 | Hig | 0.49 | 7.5 | 0.01 | Aug 6, 2021 | In JetBrains TeamCity before 2021.1, passwords in cleartext sometimes could be stored in VCS. | ||
| CVE-2021-37545 | Hig | 0.49 | 7.5 | 0.01 | Aug 6, 2021 | In JetBrains TeamCity before 2021.1.1, insufficient authentication checks for agent requests were made. | ||
| CVE-2021-31913 | Hig | 0.49 | 7.5 | 0.01 | May 11, 2021 | In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange. | ||
| CVE-2021-31910 | Hig | 0.49 | 7.5 | 0.01 | May 11, 2021 | In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible. | ||
| CVE-2021-26310 | Hig | 0.49 | 7.5 | 0.02 | May 11, 2021 | In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible. | ||
| CVE-2021-25776 | Hig | 0.49 | 7.5 | 0.01 | Feb 3, 2021 | In JetBrains TeamCity before 2020.2, an ECR token could be exposed in a build's parameters. | ||
| CVE-2020-35667 | Hig | 0.49 | 7.5 | 0.01 | Feb 3, 2021 | JetBrains TeamCity Plugin before 2020.2.85695 SSRF. Vulnerability that could potentially expose user credentials. | ||
| CVE-2020-11688 | Hig | 0.49 | 7.5 | 0.01 | Apr 22, 2020 | In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session. | ||
| CVE-2020-11687 | Hig | 0.49 | 7.5 | 0.01 | Apr 22, 2020 | In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages. | ||
| CVE-2020-7909 | Hig | 0.49 | 7.5 | 0.01 | Jan 30, 2020 | In JetBrains TeamCity before 2019.1.5, some server-stored passwords could be shown via the web UI. | ||
| CVE-2019-15042 | Hig | 0.49 | 7.5 | 0.01 | Oct 1, 2019 | An issue was discovered in JetBrains TeamCity 2018.2.4. It had no SSL certificate validation for some external https connections. This was fixed in TeamCity 2019.1. | ||
| CVE-2019-15038 | Hig | 0.49 | 7.5 | 0.01 | Oct 1, 2019 | An issue was discovered in JetBrains TeamCity 2018.2.4. The TeamCity server was not using some security-related HTTP headers. The issue was fixed in TeamCity 2019.1. | ||
| CVE-2019-12841 | Hig | 0.49 | 7.5 | 0.01 | Jul 3, 2019 | Incorrect handling of user input in ZIP extraction was detected in JetBrains TeamCity. The issue was fixed in TeamCity 2018.2.2. | ||
| CVE-2026-133097 | Hig | 0.48 | 7.4 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable |
- risk 0.49cvss 7.5epss 0.00
In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership
- risk 0.49cvss 7.5epss 0.00
In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions
- risk 0.49cvss 7.5epss 0.00
In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2021.2.3, environment variables of the "password" type could be logged in some cases.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2021.2.1, editing a user account to change its password didn't terminate sessions of the edited user.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2021.1, information disclosure via the Docker Registry connection dialog is possible.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2021.1, passwords in cleartext sometimes could be stored in VCS.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2021.1.1, insufficient authentication checks for agent requests were made.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible.
- risk 0.49cvss 7.5epss 0.02
In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2020.2, an ECR token could be exposed in a build's parameters.
- risk 0.49cvss 7.5epss 0.01
JetBrains TeamCity Plugin before 2020.2.85695 SSRF. Vulnerability that could potentially expose user credentials.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages.
- risk 0.49cvss 7.5epss 0.01
In JetBrains TeamCity before 2019.1.5, some server-stored passwords could be shown via the web UI.
- risk 0.49cvss 7.5epss 0.01
An issue was discovered in JetBrains TeamCity 2018.2.4. It had no SSL certificate validation for some external https connections. This was fixed in TeamCity 2019.1.
- risk 0.49cvss 7.5epss 0.01
An issue was discovered in JetBrains TeamCity 2018.2.4. The TeamCity server was not using some security-related HTTP headers. The issue was fixed in TeamCity 2019.1.
- risk 0.49cvss 7.5epss 0.01
Incorrect handling of user input in ZIP extraction was detected in JetBrains TeamCity. The issue was fixed in TeamCity 2018.2.2.
- risk 0.48cvss 7.4epss 0.00
In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable
Page 6 of 25