Teamcity
by Jetbrains
Source repositories
CVEs (487)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2021-26309 | Low | 0.21 | 3.3 | 0.00 | May 11, 2021 | Information disclosure in the TeamCity plugin for IntelliJ before 2020.2.2.85899 was possible because a local temporary file had Insecure Permissions. | ||
| CVE-2026-132992 | Low | 0.20 | 3.1 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible | ||
| CVE-2026-132991 | Low | 0.20 | 3.1 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible | ||
| CVE-2026-132990 | Low | 0.20 | 3.1 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible | ||
| CVE-2026-132251 | Low | 0.20 | 3.1 | 0.00 | Nov 18, 2026 | In JetBrains TeamCity before 2026.1.3 privilege escalation was possible by issuing new tokens from a restricted access token | ||
| CVE-2026-132250 | Low | 0.20 | 3.1 | 0.00 | Nov 18, 2026 | In JetBrains TeamCity before 2026.1.3 privilege escalation was possible via Basic authentication with a restricted access token | ||
| CVE-2026-49380 | Low | 0.20 | 3.1 | 0.00 | May 29, 2026 | In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible | ||
| CVE-2025-67739 | Low | 0.20 | 3.1 | 0.00 | Dec 11, 2025 | In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure | ||
| CVE-2026-133108 | Low | 0.18 | 2.7 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and session cookies | ||
| CVE-2026-132996 | Low | 0.18 | 2.7 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users | ||
| CVE-2026-132994 | Low | 0.18 | 2.7 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI | ||
| CVE-2026-132988 | Low | 0.18 | 2.7 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access | ||
| CVE-2025-68164 | Low | 0.18 | 2.7 | 0.00 | Dec 16, 2025 | In JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection test | ||
| CVE-2025-68162 | Low | 0.18 | 2.7 | 0.00 | Dec 16, 2025 | In JetBrains TeamCity before 2025.11 maven embedder allowed loading extensions via project configuration | ||
| CVE-2025-67740 | Low | 0.18 | 2.7 | 0.00 | Dec 11, 2025 | In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata | ||
| CVE-2025-31141 | Low | 0.18 | 2.7 | 0.00 | Mar 27, 2025 | In JetBrains TeamCity before 2025.03 exception could lead to credential leakage on Cloud Profiles page | ||
| CVE-2022-44622 | Low | 0.18 | 2.7 | 0.01 | Nov 3, 2022 | In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive | ||
| CVE-2021-31906 | Low | 0.18 | 2.7 | 0.01 | May 11, 2021 | In JetBrains TeamCity before 2020.2.2, audit logs were not sufficient when an administrator uploaded a file. | ||
| CVE-2020-11686 | Low | 0.18 | 2.7 | 0.01 | Apr 22, 2020 | In JetBrains TeamCity before 2019.1.4, a project administrator was able to retrieve some TeamCity server settings. | ||
| CVE-2024-41828 | Low | 0.17 | 2.6 | 0.00 | Jul 22, 2024 | In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time |
- risk 0.21cvss 3.3epss 0.00
Information disclosure in the TeamCity plugin for IntelliJ before 2020.2.2.85899 was possible because a local temporary file had Insecure Permissions.
- risk 0.20cvss 3.1epss 0.00
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible
- risk 0.20cvss 3.1epss 0.00
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible
- risk 0.20cvss 3.1epss 0.00
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible
- risk 0.20cvss 3.1epss 0.00
In JetBrains TeamCity before 2026.1.3 privilege escalation was possible by issuing new tokens from a restricted access token
- risk 0.20cvss 3.1epss 0.00
In JetBrains TeamCity before 2026.1.3 privilege escalation was possible via Basic authentication with a restricted access token
- risk 0.20cvss 3.1epss 0.00
In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible
- risk 0.20cvss 3.1epss 0.00
In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2026.2.2 the current request details debug endpoint exposed authentication headers and session cookies
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection test
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2025.11 maven embedder allowed loading extensions via project configuration
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata
- risk 0.18cvss 2.7epss 0.00
In JetBrains TeamCity before 2025.03 exception could lead to credential leakage on Cloud Profiles page
- risk 0.18cvss 2.7epss 0.01
In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive
- risk 0.18cvss 2.7epss 0.01
In JetBrains TeamCity before 2020.2.2, audit logs were not sufficient when an administrator uploaded a file.
- risk 0.18cvss 2.7epss 0.01
In JetBrains TeamCity before 2019.1.4, a project administrator was able to retrieve some TeamCity server settings.
- risk 0.17cvss 2.6epss 0.00
In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time
Page 24 of 25