JetBrains TeamCity
191 vulnérabilités publiées citent ce produit.
Tel que les CNA l’écrivent dans leurs fiches CVE (éditeur et produit) ; les versions sont les leurs.
| CVE | Versions vulnérables | Titre | Sévérité | Publiée | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2026-111096 | < 2026.2,
2026.1.4,
2025.11.8 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic build log was possible | MEDIUM 6.7 | 0.2 % | ||
| CVE-2026-111095 | < 2026.2,
2026.1.4,
2025.11.8 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic project overview was possible | HIGH 8.0 | 0.2 % | ||
| CVE-2026-111094 | < 2026.2,
2026.1.4,
2025.11.8 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution via a whitelist bypass in the build messages protocol was p | CRITICAL 9.8 | 0.4 % | ||
| CVE-2026-106219 | < 2026.2.1 | In JetBrains TeamCity before 2026.2.1 missing validation of Git submodule URLs allowed reading local repositories on the server | HIGH 7.5 | 0.7 % | ||
| CVE-2026-106218 | < 2026.1.3
2025.11.7 | In JetBrains TeamCity before 2026.1.3 2025.11.7 kotlin DSL sandbox escape leading to RCE on the server was possible | CRITICAL 10.0 | 0.3 % | ||
| CVE-2026-100255 | < 2026.2,
2026.1.4,
2025.11.8 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 administrator account takeover was possible via password reset | CRITICAL 9.8 | 0.4 % | ||
| CVE-2026-100254 | < 2026.2,
2026.1.4,
2025.11.8 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 authenticated users could execute commands on Windows servers via CRLF injection | HIGH 8.8 | 0.5 % | ||
| CVE-2026-100253 | < 2026.2,
2026.1.4,
2025.11.8 | In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possible via the versioned settings | HIGH 8.8 | 0.4 % | ||
| CVE-2026-63077 | < 2026.1.3, 2025.11.7 | In JetBrains TeamCity before 2026.1.3, 2025.11.7 unauthenticated remote code execution was possible via the agent polling protocol | CRITICAL 9.8 | 94 % | KEV | |
| CVE-2026-65907 | < 2026.1.2, 2025.11.6 | In JetBrains TeamCity before 2026.1.2, 2025.11.6 code execution in Git VCS roots was possible | CRITICAL 9.1 | 0.7 % | ||
| CVE-2026-65906 | < 2026.1.2, 2025.11.6 | In JetBrains TeamCity before 2026.1.2, 2025.11.6 сode execution via Kotlin DSL sandbox escape was possible | CRITICAL 10.0 | 0.7 % | ||
| CVE-2026-59796 | < 2026.1.2 | In JetBrains TeamCity before 2026.1.2 pipeline modification was possible due to improper permission checks | HIGH 8.1 | 0.4 % | ||
| CVE-2026-59795 | < 2026.1.2 | In JetBrains TeamCity before 2026.1.2 stored XSS via unauthenticated agent registration was possible | HIGH 8.1 | 0.3 % | ||
| CVE-2026-59794 | < 2026.1.2 | In JetBrains TeamCity before 2026.1.2 stored XSS on the cloud profile page was possible via agent-reported data | HIGH 7.3 | 0.3 % | ||
| CVE-2026-59793 | < 2026.1.2 | In JetBrains TeamCity before 2026.1.2 arbitrary file access was possible via the Perforce VCS integration | HIGH 8.8 | 0.5 % | ||
| CVE-2026-49381 | < 2026.1 | In JetBrains TeamCity before 2026.1 stored XSS on the SAML login page was possible | MEDIUM 4.8 | 0.2 % | ||
| CVE-2026-49380 | < 2026.1 | In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible | MEDIUM 6.1 | 0.2 % | ||
| CVE-2026-49379 | < 2026.1 | In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names | MEDIUM 6.5 | 0.3 % | ||
| CVE-2026-49378 | < 2026.1 | In JetBrains TeamCity before 2026.1 credentials parameters were exposed via parameter autocompletion | MEDIUM 4.3 | 0.2 % | ||
| CVE-2026-49377 | < 2025.11.2 | In JetBrains TeamCity before 2025.11.2 exposure of sensitive data via default agent parameters | MEDIUM 4.3 | 0.7 % | ||
| CVE-2026-49376 | < 2026.1 | In JetBrains TeamCity before 2026.1 insufficient username validation in the SAML plugin | MEDIUM 6.5 | 0.2 % | ||
| CVE-2026-49375 | < 2026.1,
2025.11.5 | In JetBrains TeamCity before 2026.1, 2025.11.5 reflected XSS was possible on the repository download page | MEDIUM 6.1 | 0.2 % | ||
| CVE-2026-49374 | < 2026.1 | In JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parameters | HIGH 7.6 | 0.2 % | ||
| CVE-2026-49373 | < 2026.1 | In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings | HIGH 8.8 | 25 % | ||
| CVE-2026-49372 | < 2026.1,
2025.11.5 | In JetBrains TeamCity before 2026.1, 2025.11.5 unauthenticated SSRF via build status was possible | HIGH 7.5 | 0.3 % | ||
| CVE-2026-49371 | < 2026.1.1 | In JetBrains TeamCity before 2026.1.1 reflected XSS in the keyword filter was possible | HIGH 8.2 | 0.3 % | ||
| CVE-2026-44413 | < 2026.1
2025.11.5 | In JetBrains TeamCity before 2026.1 2025.11.5 authenticated users could expose server API to unauthorised access | HIGH 8.2 | 0.3 % | ||
| CVE-2026-28196 | < 2025.11.3 | In JetBrains TeamCity before 2025.11.3 disabling versioned settings left a credentials config on disk | LOW 2.3 | 0.1 % | ||
| CVE-2026-28195 | < 2025.11.3 | In JetBrains TeamCity before 2025.11.3 missing authorization allowed project developers to add parameters to build configurations | MEDIUM 4.3 | 0.2 % | ||
| CVE-2026-28194 | < 2025.11.3 | In JetBrains TeamCity before 2025.11.3 open redirect was possible in the React project creation flow | MEDIUM 6.1 | 0.2 % | ||
| CVE-2025-68268 | < 2025.11.1 | In JetBrains TeamCity before 2025.11.1 reflected XSS was possible on the storage settings page | MEDIUM 6.1 | 0.2 % | ||
| CVE-2025-68267 | < 2025.11.1 | In JetBrains TeamCity before 2025.11.1 excessive privileges were possible due to storing GitHub personal access token instead of an installa | MEDIUM 6.5 | 0.2 % | ||
| CVE-2025-68166 | < 2025.11 | In JetBrains TeamCity before 2025.11 a DOM-based XSS was possible on the OAuth connections tab | MEDIUM 6.1 | 0.2 % | ||
| CVE-2025-68165 | < 2025.11 | In JetBrains TeamCity before 2025.11 reflected XSS was possible on VCS Root setup | MEDIUM 6.1 | 4.2 % | ||
| CVE-2025-68164 | < 2025.11 | In JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection test | LOW 2.7 | 0.2 % | ||
| CVE-2025-68163 | < 2025.11 | In JetBrains TeamCity before 2025.11 stored XSS was possible on agentpushInstall page | MEDIUM 4.8 | 0.2 % | ||
| CVE-2025-68162 | < 2025.11 | In JetBrains TeamCity before 2025.11 maven embedder allowed loading extensions via project configuration | LOW 2.7 | 0.2 % | ||
| CVE-2025-67742 | < 2025.11 | In JetBrains TeamCity before 2025.11 path traversal was possible via file upload | HIGH 7.5 | 0.8 % | ||
| CVE-2025-67741 | < 2025.11 | In JetBrains TeamCity before 2025.11 stored XSS was possible via session attribute | MEDIUM 5.4 | 0.5 % | ||
| CVE-2025-67740 | < 2025.11 | In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata | MEDIUM 5.3 | 0.2 % | ||
| CVE-2025-67739 | < 2025.11.2 | In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure | LOW 3.1 | 0.2 % | ||
| CVE-2025-59457 | < 2025.07.2 | In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on Windows | HIGH 7.7 | 0.8 % | ||
| CVE-2025-59456 | < 2025.07.2 | In JetBrains TeamCity before 2025.07.2 path traversal was possible during project archive upload | MEDIUM 5.5 | 15 % | ||
| CVE-2025-59455 | < 2025.07.2 | In JetBrains TeamCity before 2025.07.2 project isolation bypass was possible due to race condition | MEDIUM 4.2 | 0.4 % | ||
| CVE-2025-57734 | < 2025.07.1 | In JetBrains TeamCity before 2025.07.1 aWS credentials were exposed in Docker script files | MEDIUM 6.5 | 0.8 % | ||
| CVE-2025-57733 | < 2025.07.1 | In JetBrains TeamCity before 2025.07.1 sMTP injection was possible allowing modification of email content | MEDIUM 5.5 | 0.3 % | ||
| CVE-2025-57732 | < 2025.07.1 | In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership | HIGH 7.5 | 0.1 % | ||
| CVE-2025-54538 | < 2025.07 | In JetBrains TeamCity before 2025.07 password exposure was possible via command line in the "hg pull" command | MEDIUM 5.5 | 0.3 % | ||
| CVE-2025-54537 | < 2025.07 | In JetBrains TeamCity before 2025.07 user credentials were stored in plain text in memory snapshots | MEDIUM 5.5 | 0.3 % | ||
| CVE-2025-54536 | < 2025.07 | In JetBrains TeamCity before 2025.07 a CSRF was possible on GraphQL endpoint | HIGH 8.8 | 0.2 % | ||
| CVE-2025-54535 | < 2025.07 | In JetBrains TeamCity before 2025.07 password reset and email verification tokens were using weak hashing algorithms | HIGH 7.5 | 0.2 % | ||
| CVE-2025-54534 | < 2025.07 | In JetBrains TeamCity before 2025.07 reflected XSS was possible on the agentpushPreset page | MEDIUM 4.8 | 0.9 % | ||
| CVE-2025-54533 | < 2025.07 | In JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via VCS configuration | MEDIUM 4.3 | 0.2 % | ||
| CVE-2025-54532 | < 2025.07 | In JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via snapshot dependencies | MEDIUM 4.3 | 0.2 % | ||
| CVE-2025-54531 | < 2025.07 | In JetBrains TeamCity before 2025.07 path traversal was possible via plugin unpacking on Windows | CRITICAL 9.4 | 0.3 % | ||
| CVE-2025-54530 | < 2025.07 | In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions | CRITICAL 9.8 | 0.2 % | ||
| CVE-2025-54529 | < 2025.07 | In JetBrains TeamCity before 2025.07 a CSRF was possible in external OAuth login integration | HIGH 7.5 | 0.1 % | ||
| CVE-2025-54528 | < 2025.07 | In JetBrains TeamCity before 2025.07 a CSRF was possible in GitHub App connection flow | HIGH 8.8 | 0.2 % | ||
| CVE-2025-52879 | < 2025.03.3 | In JetBrains TeamCity before 2025.03.3 reflected XSS in the NPM Registry integration was possible | MEDIUM 4.8 | 1.2 % | ||
| CVE-2025-52878 | < 2025.03.3 | In JetBrains TeamCity before 2025.03.3 usernames were exposed to the users without proper permissions | MEDIUM 4.3 | 0.4 % | ||
| CVE-2025-52877 | < 2025.03.3 | In JetBrains TeamCity before 2025.03.3 reflected XSS on diskUsageBuildsStats page was possible | MEDIUM 4.8 | 37 % | ||
| CVE-2025-52876 | < 2025.03.3 | In JetBrains TeamCity before 2025.03.3 reflected XSS on the favoriteIcon page was possible | MEDIUM 5.4 | 39 % | ||
| CVE-2025-52875 | < 2025.03.3 | In JetBrains TeamCity before 2025.03.3 a DOM-based XSS at the Performance Monitor page was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2025-47854 | < 2025.03.2 | In JetBrains TeamCity before 2025.03.2 open redirect was possible on editing VCS Root page | MEDIUM 6.1 | 0.3 % | ||
| CVE-2025-47853 | < 2025.03.2 | In JetBrains TeamCity before 2025.03.2 stored XSS via Jira integration was possible | MEDIUM 5.4 | 0.8 % | ||
| CVE-2025-47852 | < 2025.03.2 | In JetBrains TeamCity before 2025.03.2 stored XSS via YouTrack integration was possible | MEDIUM 5.4 | 0.8 % | ||
| CVE-2025-47851 | < 2025.03.2 | In JetBrains TeamCity before 2025.03.2 stored XSS via GitHub Checks Webhook was possible | MEDIUM 5.4 | 2.8 % | ||
| CVE-2025-46618 | < 2025.03.1 | In JetBrains TeamCity before 2025.03.1 stored XSS was possible on Data Directory tab | MEDIUM 6.1 | 63 % | ||
| CVE-2025-46433 | < 2025.03.1 | In JetBrains TeamCity before 2025.03.1 improper path validation in loggingPreset parameter was possible | CRITICAL 9.8 | 0.6 % | ||
| CVE-2025-46432 | < 2025.03.1 | In JetBrains TeamCity before 2025.03.1 base64-encoded credentials could be exposed in build logs | MEDIUM 6.5 | 1.0 % | ||
| CVE-2025-31141 | < 2025.03 | In JetBrains TeamCity before 2025.03 exception could lead to credential leakage on Cloud Profiles page | HIGH 7.5 | 0.4 % | ||
| CVE-2025-31140 | < 2025.03 | In JetBrains TeamCity before 2025.03 stored XSS was possible on Cloud Profiles page | MEDIUM 6.1 | 28 % | ||
| CVE-2025-31139 | < 2025.03 | In JetBrains TeamCity before 2025.03 base64 encoded password could be exposed in build log | MEDIUM 6.5 | 1.0 % | ||
| CVE-2025-26492 | < 2024.12.2 | In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources | CRITICAL 9.1 | 0.4 % | ||
| CVE-2025-26493 | < 2024.12.2 | In JetBrains TeamCity before 2024.12.2 several DOM-based XSS were possible on the Code Inspection Report tab | MEDIUM 6.1 | 0.4 % | ||
| CVE-2025-24461 | < 2024.12.1 | In JetBrains TeamCity before 2024.12.1 decryption of connection secrets without proper permissions was possible via Test Connection endpoint | MEDIUM 6.5 | 0.3 % | ||
| CVE-2025-24460 | < 2024.12.1 | In JetBrains TeamCity before 2024.12.1 improper access control allowed to see Projects’ names in the agent pool | MEDIUM 4.3 | 0.3 % | ||
| CVE-2025-24459 | < 2024.12.1 | In JetBrains TeamCity before 2024.12.1 reflected XSS was possible on the Vault Connection page | MEDIUM 6.1 | 2.8 % | ||
| CVE-2024-56356 | < 2024.12 | In JetBrains TeamCity before 2024.12 insecure XMLParser configuration could lead to potential XXE attack | HIGH 7.1 | 0.2 % | ||
| CVE-2024-56355 | < 2024.12 | In JetBrains TeamCity before 2024.12 missing Content-Type header in RemoteBuildLogController response could lead to XSS | MEDIUM 5.4 | 0.8 % | ||
| CVE-2024-56354 | < 2024.12 | In JetBrains TeamCity before 2024.12 password field value were accessible to users with view settings permission | MEDIUM 5.5 | 0.3 % | ||
| CVE-2024-56353 | < 2024.12 | In JetBrains TeamCity before 2024.12 backup file exposed user credentials and session cookies | MEDIUM 6.5 | 0.3 % | ||
| CVE-2024-56352 | < 2024.12 | In JetBrains TeamCity before 2024.12 stored XSS was possible via image name on the agent details page | MEDIUM 5.4 | 0.8 % | ||
| CVE-2024-56351 | < 2024.12 | In JetBrains TeamCity before 2024.12 access tokens were not revoked after removing user roles | HIGH 8.8 | 0.3 % | ||
| CVE-2024-56350 | < 2024.12 | In JetBrains TeamCity before 2024.12 build credentials allowed unauthorized viewing of projects | MEDIUM 4.3 | 0.3 % | ||
| CVE-2024-56349 | < 2024.12 | In JetBrains TeamCity before 2024.12 improper access control allowed unauthorized users to modify build logs | MEDIUM 5.3 | 0.3 % | ||
| CVE-2024-56348 | < 2024.12 | In JetBrains TeamCity before 2024.12 improper access control allowed viewing details of unauthorized agents | MEDIUM 4.3 | 0.3 % | ||
| CVE-2024-47951 | < 2024.07.3 | In JetBrains TeamCity before 2024.07.3 stored XSS was possible via server global settings | MEDIUM 5.4 | 1.4 % | ||
| CVE-2024-47950 | < 2024.07.3 | In JetBrains TeamCity before 2024.07.3 stored XSS was possible in Backup configuration settings | MEDIUM 5.4 | 1.4 % | ||
| CVE-2024-47949 | < 2024.07.3 | In JetBrains TeamCity before 2024.07.3 path traversal allowed backup file write to arbitrary location | HIGH 7.5 | 23 % | ||
| CVE-2024-47948 | < 2024.07.3 | In JetBrains TeamCity before 2024.07.3 path traversal leading to information disclosure was possible via server backups | HIGH 7.5 | 0.5 % | ||
| CVE-2024-47161 | < 2024.07.3 | In JetBrains TeamCity before 2024.07.3 password could be exposed via Sonar runner REST API | MEDIUM 6.5 | 0.3 % | ||
| CVE-2024-43810 | < 2024.07.1 | In JetBrains TeamCity before 2024.07.1 reflected XSS was possible in the AWS Core plugin | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-43809 | < 2024.07.1 | In JetBrains TeamCity before 2024.07.1 reflected XSS was possible on the agentPushPreset page | MEDIUM 6.1 | 0.3 % | ||
| CVE-2024-43808 | < 2024.07.1 | In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin | MEDIUM 5.4 | 0.2 % | ||
| CVE-2024-43807 | < 2024.07.1 | In JetBrains TeamCity before 2024.07.1 multiple stored XSS was possible on Clouds page | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-43114 | < 2024.07.1 | In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions | HIGH 7.8 | 0.2 % | ||
| CVE-2024-41829 | < 2024.07 | In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection | HIGH 7.5 | 0.3 % | ||
| CVE-2024-41828 | < 2024.07 | In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time | MEDIUM 6.5 | 0.3 % | ||
| CVE-2024-41827 | < 2024.07 | In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration | CRITICAL 9.8 | 0.4 % | ||
| CVE-2024-41826 | < 2024.07 | In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page | MEDIUM 4.8 | 0.3 % | ||
| CVE-2024-41825 | < 2024.07 | In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-41824 | < 2024.07 | In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases | MEDIUM 6.5 | 0.3 % | ||
| CVE-2024-39879 | < 2024.03.3 | In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings | MEDIUM 5.3 | 0.3 % | ||
| CVE-2024-39878 | < 2024.03.3 | In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection | MEDIUM 5.3 | 0.3 % | ||
| CVE-2024-36470 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases | CRITICAL 9.8 | 0.5 % | ||
| CVE-2024-36378 | < 2024.03.2 | In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens | HIGH 7.5 | 0.4 % | ||
| CVE-2024-36377 | < 2024.03.2 | In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions | HIGH 8.1 | 0.3 % | ||
| CVE-2024-36376 | < 2024.03.2 | In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions | HIGH 8.1 | 0.3 % | ||
| CVE-2024-36375 | < 2024.03.2 | In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed | MEDIUM 5.3 | 0.3 % | ||
| CVE-2024-36374 | < 2024.03.2 | In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-36373 | < 2024.03.2 | In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-36372 | < 2023.05.6 | In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible | MEDIUM 6.1 | 0.3 % | ||
| CVE-2024-36371 | < 2023.05.6, 2023.11.5 | In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-36370 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via OAuth connection settings was possible | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-36369 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via issue tracker integration was possible | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-36368 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 reflected XSS via OAuth provider configuration was possible | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-36367 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 stored XSS via third-party reports was possible | MEDIUM 6.1 | 0.3 % | ||
| CVE-2024-36366 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 | 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 o | MEDIUM 6.1 | 0.3 % | ||
| CVE-2024-36365 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 | 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 | HIGH 8.1 | 0.3 % | ||
| CVE-2024-36364 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.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 | MEDIUM 6.5 | 0.3 % | ||
| CVE-2024-36363 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 several Stored XSS in code inspection reports were possible | MEDIUM 5.4 | 0.3 % | ||
| CVE-2024-36362 | < 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 | In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 path traversal allowing to read files from server was pos | MEDIUM 6.5 | 0.5 % | ||
| CVE-2024-35302 | < 2023.11 | In JetBrains TeamCity before 2023.11 stored XSS during restore from backup was possible | MEDIUM 6.1 | 0.3 % | ||
| CVE-2024-35301 | < 2024.03.1 | In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token | MEDIUM 5.5 | 0.3 % | ||
| CVE-2024-35300 | 2024.03 – < 2024.03.1 | In JetBrains TeamCity between 2024.03 and 2024.03.1 several stored XSS in the available updates page were possible | MEDIUM 6.1 | 0.3 % | ||
| CVE-2024-31140 | < 2024.03 | In JetBrains TeamCity before 2024.03 server administrators could remove arbitrary files from the server by installing tools | MEDIUM 4.9 | 0.4 % | ||
| CVE-2024-31139 | < 2024.03 | In JetBrains TeamCity before 2024.03 xXE was possible in the Maven build steps detector | HIGH 8.1 | 0.5 % | ||
| CVE-2024-31138 | < 2024.03 | In JetBrains TeamCity before 2024.03 xSS was possible via Agent Distribution settings | MEDIUM 5.4 | 75 % | ||
| CVE-2024-31137 | < 2024.03 | In JetBrains TeamCity before 2024.03 reflected XSS was possible via Space connection configuration | MEDIUM 6.8 | 0.4 % | ||
| CVE-2024-31136 | < 2024.03 | In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter | HIGH 7.4 | 0.5 % | ||
| CVE-2024-31135 | < 2024.03 | In JetBrains TeamCity before 2024.03 open redirect was possible on the login page | MEDIUM 6.1 | 0.5 % | ||
| CVE-2024-31134 | < 2024.03 | In JetBrains TeamCity before 2024.03 authenticated users without administrative permissions could register other users when self-registratio | MEDIUM 6.5 | 0.4 % | ||
| CVE-2024-29880 | < 2023.11 | In JetBrains TeamCity before 2023.11 users with access to the agent machine might obtain permissions of the user running the agent process | HIGH 7.8 | 0.2 % | ||
| CVE-2024-28174 | < 2023.11.4 | In JetBrains TeamCity before 2023.11.4 presigned URL generation requests in S3 Artifact Storage plugin were authorized improperly | MEDIUM 5.8 | 0.3 % | ||
| CVE-2024-28173 | 2023.11 – < 2023.11.4 | In JetBrains TeamCity between 2023.11 and 2023.11.4 custom build parameters of the "password" type could be disclosed | MEDIUM 4.3 | 0.5 % | ||
| CVE-2024-27199 | < 2023.11.4 | In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible | HIGH 7.3 | 100 % | KEV | |
| CVE-2024-27198 | < 2023.11.4 | In JetBrains TeamCity before 2023.11.4 authentication bypass allowing to perform admin actions was possible | CRITICAL 9.8 | 100 % | KEV | |
| CVE-2024-24942 | < 2023.11.3 | In JetBrains TeamCity before 2023.11.3 path traversal allowed reading data within JAR archives | MEDIUM 5.3 | 32 % | ||
| CVE-2024-23917 | < 2023.11.3 | In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible | CRITICAL 9.8 | 54 % | ||
| CVE-2024-24938 | < 2023.11.2 | In JetBrains TeamCity before 2023.11.2 limited directory traversal was possible in the Kotlin DSL documentation | MEDIUM 5.3 | 0.7 % | ||
| CVE-2024-24937 | < 2023.11.2 | In JetBrains TeamCity before 2023.11.2 stored XSS via agent distribution was possible | MEDIUM 5.4 | 0.4 % | ||
| CVE-2024-24936 | < 2023.11.2 | In JetBrains TeamCity before 2023.11.2 access control at the S3 Artifact Storage plugin endpoint was missed | MEDIUM 5.3 | 0.3 % | ||
| CVE-2023-50870 | < 2023.11.1 | In JetBrains TeamCity before 2023.11.1 a CSRF on login was possible | HIGH 8.8 | 0.3 % | ||
| CVE-2023-43566 | < 2023.05.4 | In JetBrains TeamCity before 2023.05.4 stored XSS was possible during nodes configuration | MEDIUM 5.4 | 1.0 % | ||
| CVE-2023-42793 | < 2023.05.4 | In JetBrains TeamCity before 2023.05.4 authentication bypass leading to RCE on TeamCity Server was possible | CRITICAL 9.8 | 100 % | KEV | |
| CVE-2023-41250 | < 2023.05.3 | In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during user registration | MEDIUM 6.1 | 0.4 % | ||
| CVE-2023-41249 | < 2023.05.3 | In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during copying Build Step | MEDIUM 6.1 | 56 % | ||
| CVE-2023-41248 | < 2023.05.3 | In JetBrains TeamCity before 2023.05.3 stored XSS was possible during Cloud Profiles configuration | MEDIUM 5.4 | 0.4 % | ||
| CVE-2023-39175 | < 2023.05.2 | In JetBrains TeamCity before 2023.05.2 reflected XSS via GitHub integration was possible | MEDIUM 6.1 | 1.0 % | ||
| CVE-2023-39174 | < 2023.05.2 | In JetBrains TeamCity before 2023.05.2 a ReDoS attack was possible via integration with issue trackers | HIGH 7.5 | 1.7 % | ||
| CVE-2023-39173 | < 2023.05.2 | In JetBrains TeamCity before 2023.05.2 a token with limited permissions could be used to gain full account access | HIGH 8.8 | 0.4 % | ||
| CVE-2023-38067 | < 2023.05.1 | In JetBrains TeamCity before 2023.05.1 build parameters of the "password" type could be written to the agent log | MEDIUM 6.5 | 0.5 % | ||
| CVE-2023-38066 | < 2023.05.1 | In JetBrains TeamCity before 2023.05.1 reflected XSS via the Referer header was possible during artifact downloads | MEDIUM 6.1 | 1.0 % | ||
| CVE-2023-38065 | < 2023.05.1 | In JetBrains TeamCity before 2023.05.1 stored XSS while viewing the build log was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2023-38064 | < 2023.05.1 | In JetBrains TeamCity before 2023.05.1 build chain parameters of the "password" type could be written to the agent log | MEDIUM 6.5 | 0.5 % | ||
| CVE-2023-38063 | < 2023.05.1 | In JetBrains TeamCity before 2023.05.1 stored XSS while running custom builds was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2023-38062 | < 2023.05.1 | In JetBrains TeamCity before 2023.05.1 parameters of the "password" type could be shown in the UI in certain composite build configurations | MEDIUM 6.5 | 1.4 % | ||
| CVE-2023-38061 | < 2023.05.1 | In JetBrains TeamCity before 2023.05.1 stored XSS when using a custom theme was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2015-1313 | 8.0.1 – < 9.0.2 | JetBrains TeamCity 8 and 9 before 9.0.2 allows bypass of account-creation restrictions via a crafted request because the required request da | MEDIUM 6.5 | 0.6 % | ||
| CVE-2023-34229 | < 2023.05 | In JetBrains TeamCity before 2023.05 stored XSS in GitLab Connection page was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2023-34228 | < 2023.05 | In JetBrains TeamCity before 2023.05 authentication checks were missing – 2FA was not checked for some sensitive account actions | MEDIUM 6.5 | 0.4 % | ||
| CVE-2023-34227 | < 2023.05 | In JetBrains TeamCity before 2023.05 a specific endpoint was vulnerable to brute force attacks | HIGH 7.5 | 0.5 % | ||
| CVE-2023-34226 | < 2023.05 | In JetBrains TeamCity before 2023.05 reflected XSS in the Subscriptions page was possible | MEDIUM 6.1 | 1.0 % | ||
| CVE-2023-34225 | < 2023.05 | In JetBrains TeamCity before 2023.05 stored XSS in the NuGet feed page was possible | MEDIUM 5.4 | 61 % | ||
| CVE-2023-34224 | < 2023.05 | In JetBrains TeamCity before 2023.05 open redirect during oAuth configuration was possible | MEDIUM 4.8 | 0.3 % | ||
| CVE-2023-34223 | < 2023.05 | In JetBrains TeamCity before 2023.05 parameters of the "password" type from build dependencies could be logged in some cases | MEDIUM 5.3 | 1.3 % | ||
| CVE-2023-34222 | < 2023.05 | In JetBrains TeamCity before 2023.05 possible XSS in the Plugin Vendor URL was possible | MEDIUM 6.1 | 1.0 % | ||
| CVE-2023-34221 | < 2023.05 | In JetBrains TeamCity before 2023.05 stored XSS in the Show Connection page was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2023-34220 | < 2023.05 | In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible | MEDIUM 5.4 | 61 % | ||
| CVE-2023-34219 | < 2023.05 | In JetBrains TeamCity before 2023.05 improper permission checks allowed users without appropriate permissions to edit Build Configuration se | MEDIUM 4.3 | 0.4 % | ||
| CVE-2023-34218 | < 2023.05 | In JetBrains TeamCity before 2023.05 bypass of permission checks allowing to perform admin actions was possible | CRITICAL 9.8 | 0.6 % | ||
| CVE-2022-48428 | < 2022.10.3 | In JetBrains TeamCity before 2022.10.3 stored XSS on the SSH keys page was possible | MEDIUM 5.4 | 68 % | ||
| CVE-2022-48427 | < 2022.10.3 | In JetBrains TeamCity before 2022.10.3 stored XSS on “Pending changes” and “Changes” tabs was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2022-48426 | < 2022.10.3 | In JetBrains TeamCity before 2022.10.3 stored XSS in Perforce connection settings was possible | MEDIUM 5.4 | 1.0 % | ||
| CVE-2022-48344 | < 2022.10.2 | In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the group creation process. | MEDIUM 6.1 | 0.4 % | ||
| CVE-2022-48343 | < 2022.10.2 | In JetBrains TeamCity before 2022.10.2 there was an XSS vulnerability in the user creation process. | MEDIUM 6.1 | 59 % | ||
| CVE-2022-48342 | < 2022.10.2 | In JetBrains TeamCity before 2022.10.2 jVMTI was enabled by default on agents. | CRITICAL 9.8 | 0.3 % | ||
| CVE-2022-46831 | 2022.10 – < 2022.10.1 | In JetBrains TeamCity between 2022.10 and 2022.10.1 connecting to AWS using the "Default Credential Provider Chain" allowed TeamCity project | MEDIUM 6.6 | 0.5 % | ||
| CVE-2022-46830 | 2022.10 – < 2022.10.1 | In JetBrains TeamCity between 2022.10 and 2022.10.1 a custom STS endpoint allowed internal port scanning. | MEDIUM 5.3 | 0.5 % | ||
| CVE-2022-44646 | 2022.10 – < 2022.10 | In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings | MEDIUM 5.3 | 0.4 % | ||
| CVE-2022-44624 | 2022.10 – < 2022.10 | In JetBrains TeamCity version before 2022.10, Password parameters could be exposed in the build log if they contained special characters | HIGH 7.5 | 0.6 % | ||
| CVE-2022-44623 | 2022.10 – < 2022.10 | In JetBrains TeamCity version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings | HIGH 7.5 | 0.6 % | ||
| CVE-2022-44622 | 2022.10 – < 2022.10 ; 2021.2 – < 2021.2* | In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive | MEDIUM 5.3 | 0.5 % | ||
| CVE-2022-40979 | 2022.04.4 – < 2022.04.4 | In JetBrains TeamCity before 2022.04.4 environmental variables of "password" type could be logged when using custom Perforce executable | MEDIUM 5.3 | 0.4 % | ||
| CVE-2022-38133 | 2022.04.3 – < 2022.04.3 | In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases | MEDIUM 5.3 | 0.5 % | ||
| CVE-2022-36322 | 2022.04.2 – < 2022.04.2 | In JetBrains TeamCity before 2022.04.2 build parameter injection was possible | HIGH 8.8 | 0.7 % | ||
| CVE-2022-36321 | 2022.04.2 – < 2022.04.2 | In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases | MEDIUM 6.5 | 1.9 % | ||
| CVE-2022-29929 | 2022.04 – < 2022.04 | In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible | MEDIUM 6.1 | 0.5 % | ||
| CVE-2022-29928 | 2022.04 – < 2022.04 | In JetBrains TeamCity before 2022.04 leak of secrets in TeamCity agent logs was possible | MEDIUM 4.9 | 0.5 % | ||
| CVE-2022-29927 | 2022.04 – < 2022.04 | In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible | MEDIUM 6.1 | 1.6 % |