Teamcity
by Jetbrains
Source repositories
CVEs (487)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-133020 | Hig | 0.48 | 7.4 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.1.5 untrusted build approval for GitHub fork pull requests could be bypassed | ||
| CVE-2024-41827 | Hig | 0.48 | 7.4 | 0.00 | Jul 22, 2024 | In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration | ||
| CVE-2024-31136 | Hig | 0.48 | 7.4 | 0.01 | Mar 28, 2024 | In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter | ||
| CVE-2026-133093 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject settings | ||
| CVE-2026-133090 | Hig | 0.47 | 7.2 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other projects | ||
| CVE-2026-133088 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via FreeMarker notification templates | ||
| CVE-2026-133079 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL settings | ||
| CVE-2026-133078 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox | ||
| CVE-2026-133077 | Hig | 0.47 | 7.2 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import | ||
| CVE-2026-133026 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters | ||
| CVE-2026-133023 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Kotlin DSL compiler arguments | ||
| CVE-2026-133014 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox | ||
| CVE-2026-132912 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via class injection in the Kotlin DSL sandbox | ||
| CVE-2026-132898 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file write on the server was possible via Kotlin DSL settings | ||
| CVE-2026-132896 | Hig | 0.47 | 7.2 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4 remote code execution was possible via Kubernetes Executor settings | ||
| CVE-2026-132241 | Hig | 0.47 | 7.3 | 0.00 | Nov 18, 2026 | In JetBrains TeamCity before 2026.1.3, 2025.11.7 XXE in the .NET build steps auto-discovery was possible | ||
| CVE-2026-132235 | Hig | 0.47 | 7.2 | 0.01 | Nov 18, 2026 | In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in project import archives | ||
| CVE-2026-59794 | Hig | 0.47 | 7.3 | 0.00 | Jul 10, 2026 | In JetBrains TeamCity before 2026.1.2 stored XSS on the cloud profile page was possible via agent-reported data | ||
| CVE-2026-49373 | Hig | 0.47 | 7.1 | 0.33 | May 29, 2026 | In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings | ||
| CVE-2019-15036 | Hig | 0.47 | 7.2 | 0.02 | Oct 2, 2019 | An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could execute any command on the server machine. The issue was fixed in TeamCity 2018.2.5 and 2019.1. |
- risk 0.48cvss 7.4epss 0.00
In JetBrains TeamCity before 2026.1.5 untrusted build approval for GitHub fork pull requests could be bypassed
- risk 0.48cvss 7.4epss 0.00
In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration
- risk 0.48cvss 7.4epss 0.01
In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject settings
- risk 0.47cvss 7.2epss 0.00
In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other projects
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via FreeMarker notification templates
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL settings
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox
- risk 0.47cvss 7.2epss 0.00
In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Kotlin DSL compiler arguments
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via class injection in the Kotlin DSL sandbox
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file write on the server was possible via Kotlin DSL settings
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.2, 2026.1.4 remote code execution was possible via Kubernetes Executor settings
- risk 0.47cvss 7.3epss 0.00
In JetBrains TeamCity before 2026.1.3, 2025.11.7 XXE in the .NET build steps auto-discovery was possible
- risk 0.47cvss 7.2epss 0.01
In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in project import archives
- risk 0.47cvss 7.3epss 0.00
In JetBrains TeamCity before 2026.1.2 stored XSS on the cloud profile page was possible via agent-reported data
- risk 0.47cvss 7.1epss 0.33
In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings
- risk 0.47cvss 7.2epss 0.02
An issue was discovered in JetBrains TeamCity 2018.2.4. A TeamCity Project administrator could execute any command on the server machine. The issue was fixed in TeamCity 2018.2.5 and 2019.1.
Page 7 of 25