Export limit exceeded: 362508 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (580 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-57923 | 1 Jetbrains | 1 Youtrack | 2026-06-26 | 5.3 Medium |
| In JetBrains YouTrack before 2026.2.16593 improper authorisation in the app configurations endpoint allowed modifying project settings | ||||
| CVE-2026-57924 | 1 Jetbrains | 1 Youtrack | 2026-06-26 | 4.3 Medium |
| In JetBrains YouTrack before 2026.2.16593 default role configuration exposed excessive user profile details | ||||
| CVE-2026-57925 | 1 Jetbrains | 1 Youtrack | 2026-06-26 | 4.3 Medium |
| In JetBrains YouTrack before 2026.2.16593 improper access control allowed reading saved queries and tags | ||||
| CVE-2026-57926 | 1 Jetbrains | 1 Youtrack | 2026-06-26 | 2.6 Low |
| In JetBrains YouTrack before 2026.2.16593 the websandbox bridge was vulnerable to a prototype pollution attack | ||||
| CVE-2026-57921 | 1 Jetbrains | 1 Youtrack | 2026-06-26 | 4.3 Medium |
| In JetBrains YouTrack before 2026.2.16593 improper access control allowed reading users' private data via the comment templates endpoint | ||||
| CVE-2026-57922 | 1 Jetbrains | 1 Youtrack | 2026-06-26 | 3.1 Low |
| In JetBrains YouTrack before 2026.2.16593 project settings disclosure via the MCP was possible | ||||
| CVE-2026-53914 | 1 Jetbrains | 1 Kotlin | 2026-06-26 | 6.7 Medium |
| In JetBrains Kotlin before 2.4.20 code execution was possible via unsafe deserialization in the build cache metadata | ||||
| CVE-2026-53915 | 1 Jetbrains | 1 Goland | 2026-06-25 | 7.1 High |
| In JetBrains GoLand before 2026.1.3 remote code execution was possible via untrusted project configuration | ||||
| CVE-2026-50242 | 1 Jetbrains | 1 Hub | 2026-06-22 | 10 Critical |
| In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 authentication bypass via direct database access leading to administrative access was possible | ||||
| CVE-2026-56142 | 1 Jetbrains | 1 Hub | 2026-06-22 | 9.6 Critical |
| In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 privilege escalation by attaching authentication details to accounts was possible | ||||
| CVE-2026-56141 | 1 Jetbrains | 1 Hub | 2026-06-22 | 9.8 Critical |
| In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 account takeover via predictable restore codes was possible | ||||
| CVE-2026-49373 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 7.1 High |
| In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings | ||||
| CVE-2026-49374 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 7.6 High |
| In JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parameters | ||||
| CVE-2026-49375 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 6.1 Medium |
| In JetBrains TeamCity before 2026.1, 2025.11.5 reflected XSS was possible on the repository download page | ||||
| CVE-2026-49376 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 6.5 Medium |
| In JetBrains TeamCity before 2026.1 insufficient username validation in the SAML plugin | ||||
| CVE-2026-49377 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 4.3 Medium |
| In JetBrains TeamCity before 2025.11.2 exposure of sensitive data via default agent parameters | ||||
| CVE-2026-49378 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 4.3 Medium |
| In JetBrains TeamCity before 2026.1 credentials parameters were exposed via parameter autocompletion | ||||
| CVE-2026-49379 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 6.5 Medium |
| In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names | ||||
| CVE-2026-49380 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 3.1 Low |
| In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible | ||||
| CVE-2026-49381 | 1 Jetbrains | 1 Teamcity | 2026-06-02 | 3.4 Low |
| In JetBrains TeamCity before 2026.1 stored XSS on the SAML login page was possible | ||||