Vulnerabilities (CVE)

Filtered by vendor Jetbrains Subscribe
Total 582 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-41827 1 Jetbrains 1 Teamcity 2026-06-17 N/A 7.4 HIGH
In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration
CVE-2024-41826 1 Jetbrains 1 Teamcity 2026-06-17 N/A 3.5 LOW
In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page
CVE-2024-41825 1 Jetbrains 1 Teamcity 2026-06-17 N/A 4.6 MEDIUM
In JetBrains TeamCity before 2024.07 stored XSS was possible on the Code Inspection tab
CVE-2024-41824 1 Jetbrains 1 Teamcity 2026-06-17 N/A 6.4 MEDIUM
In JetBrains TeamCity before 2024.07 parameters of the "password" type could leak into the build log in some specific cases
CVE-2024-39879 1 Jetbrains 1 Teamcity 2026-06-17 N/A 5.0 MEDIUM
In JetBrains TeamCity before 2024.03.3 application token could be exposed in EC2 Cloud Profile settings
CVE-2024-39878 1 Jetbrains 1 Teamcity 2026-06-17 N/A 4.1 MEDIUM
In JetBrains TeamCity before 2024.03.3 private key could be exposed via testing GitHub App Connection
CVE-2024-38507 1 Jetbrains 1 Hub 2026-06-17 N/A 3.5 LOW
In JetBrains Hub before 2024.2.34646 stored XSS via project description was possible
CVE-2024-38506 1 Jetbrains 1 Youtrack 2026-06-17 N/A 6.3 MEDIUM
In JetBrains YouTrack before 2024.2.34646 user without appropriate permissions could enable the auto-attach option for workflows
CVE-2024-38505 1 Jetbrains 1 Youtrack 2026-06-17 N/A 5.3 MEDIUM
In JetBrains YouTrack before 2024.2.34646 user access token was sent to the third-party site
CVE-2024-38504 1 Jetbrains 1 Youtrack 2026-06-17 N/A 4.3 MEDIUM
In JetBrains YouTrack before 2024.2.34646 the Guest User Account was enabled for attaching files to articles
CVE-2024-37051 1 Jetbrains 13 Aqua, Clion, Datagrip and 10 more 2026-06-17 N/A 9.3 CRITICAL
GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; Aqua 2024.1.2; CLion 2023.1.7, 2023.2.4, 2023.3.5, 2024.1.3, 2024.2 EAP2; DataGrip 2023.1.3, 2023.2.4, 2023.3.5, 2024.1.4; DataSpell 2023.1.6, 2023.2.7, 2023.3.6, 2024.1.2, 2024.2 EAP1; GoLand 2023.1.6, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; MPS 2023.2.1, 2023.3.1, 2024.1 EAP2; PhpStorm 2023.1.6, 2023.2.6, 2023.3.7, 2024.1.3, 2024.2 EAP3; PyCharm 2023.1.6, 2023.2.7, 2023.3.6, 2024.1.3, 2024.2 EAP2; Rider 2023.1.7, 2023.2.5, 2023.3.6, 2024.1.3; RubyMine 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP4; RustRover 2024.1.1; WebStorm 2023.1.6, 2023.2.7, 2023.3.7, 2024.1.4
CVE-2024-36470 1 Jetbrains 1 Teamcity 2026-06-17 N/A 8.1 HIGH
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases
CVE-2024-36378 1 Jetbrains 1 Teamcity 2026-06-17 N/A 5.9 MEDIUM
In JetBrains TeamCity before 2024.03.2 server was susceptible to DoS attacks with incorrect auth tokens
CVE-2024-36377 1 Jetbrains 1 Teamcity 2026-06-17 N/A 6.5 MEDIUM
In JetBrains TeamCity before 2024.03.2 certain TeamCity API endpoints did not check user permissions
CVE-2024-36376 1 Jetbrains 1 Teamcity 2026-06-17 N/A 6.5 MEDIUM
In JetBrains TeamCity before 2024.03.2 users could perform actions that should not be available to them based on their permissions
CVE-2024-36375 1 Jetbrains 1 Teamcity 2026-06-17 N/A 5.3 MEDIUM
In JetBrains TeamCity before 2024.03.2 technical information regarding TeamCity server could be exposed
CVE-2024-36374 1 Jetbrains 1 Teamcity 2026-06-17 N/A 4.6 MEDIUM
In JetBrains TeamCity before 2024.03.2 stored XSS via build step settings was possible
CVE-2024-36373 1 Jetbrains 1 Teamcity 2026-06-17 N/A 4.6 MEDIUM
In JetBrains TeamCity before 2024.03.2 several stored XSS in untrusted builds settings were possible
CVE-2024-36372 1 Jetbrains 1 Teamcity 2026-06-17 N/A 4.6 MEDIUM
In JetBrains TeamCity before 2023.05.6 reflected XSS on the subscriptions page was possible
CVE-2024-36371 1 Jetbrains 1 Teamcity 2026-06-17 N/A 4.6 MEDIUM
In JetBrains TeamCity before 2023.05.6, 2023.11.5 stored XSS in Commit status publisher was possible