26 results · Clear filters · Feed
-
Low 3.1
In JetBrains TeamCity before 2026.1 open redirect in the SAML plugin was possible
-
Low 3.4
In JetBrains TeamCity before 2026.1 stored XSS on the SAML login page was possible
-
Low 2.3
In JetBrains TeamCity before 2025.11.3 disabling versioned settings left a credentials config on disk
-
Low 2.7
In JetBrains TeamCity before 2025.11 port enumeration was possible via the Perforce connection test
-
Low 3.5
In JetBrains TeamCity before 2025.11 stored XSS was possible on agentpushInstall page
-
Low 2.7
In JetBrains TeamCity before 2025.11 maven embedder allowed loading extensions via project configuration
-
Low 3.8
In JetBrains TeamCity before 2025.11 path traversal was possible via file upload
-
Low 2.7
In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata
-
Low 3.1
In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure
-
Low 3.7
In JetBrains TeamCity before 2025.07 a CSRF was possible in external OAuth login integration
-
Low 3.5CVE-2025-46618 EPSS 63%
In JetBrains TeamCity before 2025.03.1 stored XSS was possible on Data Directory tab
-
Low 2.7
In JetBrains TeamCity before 2025.03 exception could lead to credential leakage on Cloud Profiles page
-
Low 3.5
In JetBrains TeamCity before 2024.07.3 stored XSS was possible via server global settings
-
Low 3.5
In JetBrains TeamCity before 2024.07.3 stored XSS was possible in Backup configuration settings
-
Low 3.5
In JetBrains TeamCity before 2024.07.1 reflected XSS was possible on the agentPushPreset page
-
Low 3.7
In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin
-
Low 3.5
In JetBrains TeamCity before 2024.07 an OAuth code for JetBrains Space could be stolen via Space Application connection
-
Low 2.6
In JetBrains TeamCity before 2024.07 comparison of authorization tokens took non-constant time
-
Low 3.5
In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page
-
Low 3.5
In JetBrains TeamCity between 2024.03 and 2024.03.1 several stored XSS in the available updates page were possible
-
Low 3.5
In JetBrains TeamCity before 2023.05.4 stored XSS was possible during nodes configuration
-
Low 3.5
In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during user registration
-
Low 2.7
In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive
-
Low 2.2
In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings
-
Low 3.2
In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases
-
Low 3.7
In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible