26 results · Clear filters · Feed
-
High 8.0
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic project overview was possible
-
High 8.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution via a whitelist bypass in the build mess…
-
High 8.8
In JetBrains TeamCity before 2026.1.3 2025.11.7 kotlin DSL sandbox escape leading to RCE on the server was possible
-
High 8.1
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 administrator account takeover was possible via password reset
-
High 8.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 authenticated users could execute commands on Windows servers …
-
High 8.8
In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 sandbox escape leading to code execution was possible via the …
-
High 8.8
In JetBrains TeamCity before 2026.1.2, 2025.11.6 сode execution via Kotlin DSL sandbox escape was possible
-
High 8.1
In JetBrains TeamCity before 2026.1.2 pipeline modification was possible due to improper permission checks
-
High 8.1CVE-2026-59795 Public exploit
In JetBrains TeamCity before 2026.1.2 stored XSS via unauthenticated agent registration was possible
-
High 7.3
In JetBrains TeamCity before 2026.1.2 stored XSS on the cloud profile page was possible via agent-reported data
-
High 8.8
In JetBrains TeamCity before 2026.1.2 arbitrary file access was possible via the Perforce VCS integration
-
High 7.5
In JetBrains TeamCity before 2026.1, 2025.11.5 unauthenticated SSRF via build status was possible
-
High 7.6
In JetBrains TeamCity before 2026.1 improper permission checks exposed build configuration parameters
-
High 7.1CVE-2026-49373 EPSS 33%
In JetBrains TeamCity before 2026.1 remote code execution was possible via Perforce connection settings
-
High 7.1
In JetBrains TeamCity before 2026.1.1 reflected XSS in the keyword filter was possible
-
High 8.2
In JetBrains TeamCity before 2026.1 2025.11.5 authenticated users could expose server API to unauthorised access
-
High 7.7
In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on Windows
-
High 7.5
In JetBrains TeamCity before 2025.07.1 privilege escalation was possible due to incorrect directory ownership
-
High 7.5
In JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions
-
High 7.7
In JetBrains TeamCity before 2025.07 path traversal was possible via plugin unpacking on Windows
-
High 7.7
In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources
-
High 7.5
In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions
-
High 7.4
In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration
-
High 8.1
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific …
-
High 7.4
In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter
-
High 7.3
In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible
KEV Apr 20, 2026