Teamcity
by Jetbrains
Source repositories
CVEs (487)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-132939 | Med | 0.44 | 6.8 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Maven settings health report was possible | ||
| CVE-2026-132921 | Med | 0.44 | 6.8 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management | ||
| CVE-2026-111096 | Med | 0.44 | 6.7 | 0.00 | Oct 15, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic build log was possible | ||
| CVE-2024-36365 | Med | 0.44 | 6.8 | 0.00 | May 29, 2024 | 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-2024-31137 | Med | 0.44 | 6.8 | 0.00 | Mar 28, 2024 | In JetBrains TeamCity before 2024.03 reflected XSS was possible via Space connection configuration | ||
| CVE-2026-132933 | Med | 0.43 | 6.6 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2 privilege escalation of project-scoped access tokens via concurrent project deletion was possible | ||
| CVE-2026-132246 | Med | 0.43 | 6.6 | 0.00 | Nov 18, 2026 | In JetBrains TeamCity before 2026.1.3, 2025.11.7 privilege escalation to system administrator was possible after disabling per-project permissions | ||
| CVE-2022-46831 | Med | 0.43 | 6.6 | 0.01 | Dec 8, 2022 | In JetBrains TeamCity between 2022.10 and 2022.10.1 connecting to AWS using the "Default Credential Provider Chain" allowed TeamCity project administrators to access AWS resources normally limited to TeamCity system administrators. | ||
| CVE-2026-133104 | Med | 0.42 | 6.4 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible | ||
| CVE-2026-133101 | Med | 0.42 | 6.5 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page | ||
| CVE-2026-133099 | Med | 0.42 | 6.5 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator | ||
| CVE-2026-133043 | Med | 0.42 | 6.5 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other projects | ||
| CVE-2026-133034 | Med | 0.42 | 6.4 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible | ||
| CVE-2026-133030 | Med | 0.42 | 6.5 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected credentials | ||
| CVE-2026-133029 | Med | 0.42 | 6.5 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1 missing authorization allowed guests to push VCS labels using stored VCS credentials | ||
| CVE-2026-133028 | Med | 0.42 | 6.5 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs | ||
| CVE-2026-132940 | Med | 0.42 | 6.4 | 0.01 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible | ||
| CVE-2026-132937 | Med | 0.42 | 6.5 | 0.00 | Nov 19, 2026 | In JetBrains TeamCity before 2026.2, 2026.1.4 arbitrary file write via read-write file channels in the Kotlin DSL sandbox was possible | ||
| CVE-2026-106219 | Med | 0.42 | 6.5 | 0.01 | Oct 6, 2026 | In JetBrains TeamCity before 2026.2.1 missing validation of Git submodule URLs allowed reading local repositories on the server | ||
| CVE-2026-49379 | Med | 0.42 | 6.5 | 0.00 | May 29, 2026 | In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names |
- risk 0.44cvss 6.8epss 0.00
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Maven settings health report was possible
- risk 0.44cvss 6.8epss 0.00
In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management
- risk 0.44cvss 6.7epss 0.00
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic build log was possible
- risk 0.44cvss 6.8epss 0.00
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
- risk 0.44cvss 6.8epss 0.00
In JetBrains TeamCity before 2024.03 reflected XSS was possible via Space connection configuration
- risk 0.43cvss 6.6epss 0.00
In JetBrains TeamCity before 2026.2 privilege escalation of project-scoped access tokens via concurrent project deletion was possible
- risk 0.43cvss 6.6epss 0.00
In JetBrains TeamCity before 2026.1.3, 2025.11.7 privilege escalation to system administrator was possible after disabling per-project permissions
- risk 0.43cvss 6.6epss 0.01
In JetBrains TeamCity between 2022.10 and 2022.10.1 connecting to AWS using the "Default Credential Provider Chain" allowed TeamCity project administrators to access AWS resources normally limited to TeamCity system administrators.
- risk 0.42cvss 6.4epss 0.00
In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible
- risk 0.42cvss 6.5epss 0.00
In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page
- risk 0.42cvss 6.5epss 0.01
In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator
- risk 0.42cvss 6.5epss 0.00
In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other projects
- risk 0.42cvss 6.4epss 0.00
In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible
- risk 0.42cvss 6.5epss 0.00
In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected credentials
- risk 0.42cvss 6.5epss 0.00
In JetBrains TeamCity before 2026.2.1 missing authorization allowed guests to push VCS labels using stored VCS credentials
- risk 0.42cvss 6.5epss 0.00
In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs
- risk 0.42cvss 6.4epss 0.01
In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible
- risk 0.42cvss 6.5epss 0.00
In JetBrains TeamCity before 2026.2, 2026.1.4 arbitrary file write via read-write file channels in the Kotlin DSL sandbox was possible
- risk 0.42cvss 6.5epss 0.01
In JetBrains TeamCity before 2026.2.1 missing validation of Git submodule URLs allowed reading local repositories on the server
- risk 0.42cvss 6.5epss 0.00
In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names
Page 10 of 25