| CVE-2024-41825 | MEDIO5.4 | In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab | 22/07/2024 |
| CVE-2024-41824 | MEDIO6.5 | In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases | 22/07/2024 |
| CVE-2024-39879 | MEDIO5.3 | In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings | 01/07/2024 |
| CVE-2024-39878 | MEDIO5.3 | In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection | 01/07/2024 |
| CVE-2024-36470 | CRÍTICO9.8 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases | 29/05/2024 |
| CVE-2024-36378 | ALTO7.5 | In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens | 29/05/2024 |
| CVE-2024-36377 | ALTO8.1 | In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions | 29/05/2024 |
| CVE-2024-36376 | ALTO8.1 | In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions | 29/05/2024 |
| CVE-2024-36375 | MEDIO5.3 | In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed | 29/05/2024 |
| CVE-2024-36374 | MEDIO5.4 | In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible | 29/05/2024 |
| CVE-2024-36373 | MEDIO5.4 | In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible | 29/05/2024 |
| CVE-2024-36372 | MEDIO6.1 | In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible | 29/05/2024 |
| CVE-2024-36371 | MEDIO5.4 | In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible | 29/05/2024 |
| CVE-2024-36370 | MEDIO5.4 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was possible | 29/05/2024 |
| CVE-2024-36369 | MEDIO5.4 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was possible | 29/05/2024 |
| CVE-2024-36368 | MEDIO5.4 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration was possible | 29/05/2024 |
| CVE-2024-36367 | MEDIO6.1 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible | 29/05/2024 |
| CVE-2024-36366 | MEDIO6.1 | 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 operations | 29/05/2024 |
| CVE-2024-36365 | ALTO8.1 | 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 | 29/05/2024 |
| CVE-2024-36364 | MEDIO6.5 | 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 publisher build features was possible | 29/05/2024 |