Skip to content
OpenAdvisories

Product · JetBrains

TeamCity

191 known vulnerabilities.

132 results · Clear filters · Feed

  • Medium 6.7

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the classic build log was possible

  • Medium 6.5

    In JetBrains TeamCity before 2026.2.1 missing validation of Git submodule URLs allowed reading local repositories on th…

  • Medium 4.3

    In JetBrains TeamCity before 2025.11.2 exposure of sensitive data via default agent parameters

  • Medium 6.5

    In JetBrains TeamCity before 2026.1 credentials could be exposed in thread names

  • Medium 4.3

    In JetBrains TeamCity before 2026.1 credentials parameters were exposed via parameter autocompletion

  • Medium 6.1

    In JetBrains TeamCity before 2026.1, 2025.11.5 reflected XSS was possible on the repository download page

  • Medium 6.5

    In JetBrains TeamCity before 2026.1 insufficient username validation in the SAML plugin

  • Medium 4.3

    In JetBrains TeamCity before 2025.11.3 missing authorization allowed project developers to add parameters to build conf…

  • Medium 4.3

    In JetBrains TeamCity before 2025.11.3 open redirect was possible in the React project creation flow

  • Medium 5.4

    In JetBrains TeamCity before 2025.11.1 reflected XSS was possible on the storage settings page

  • Medium 6.5

    In JetBrains TeamCity before 2025.11.1 excessive privileges were possible due to storing GitHub personal access token i…

  • Medium 5.4

    In JetBrains TeamCity before 2025.11 a DOM-based XSS was possible on the OAuth connections tab

  • Medium 5.4

    In JetBrains TeamCity before 2025.11 reflected XSS was possible on VCS Root setup

  • Medium 4.8

    In JetBrains TeamCity before 2025.11 stored XSS was possible via session attribute

  • Medium 5.5
    CVE-2025-59456 EPSS 15%

    In JetBrains TeamCity before 2025.07.2 path traversal was possible during project archive upload

  • Medium 4.2

    In JetBrains TeamCity before 2025.07.2 project isolation bypass was possible due to race condition

  • Medium 4.3

    In JetBrains TeamCity before 2025.07.1 aWS credentials were exposed in Docker script files

  • Medium 5.5

    In JetBrains TeamCity before 2025.07.1 sMTP injection was possible allowing modification of email content

  • Medium 5.5

    In JetBrains TeamCity before 2025.07 password exposure was possible via command line in the "hg pull" command

  • Medium 5.5

    In JetBrains TeamCity before 2025.07 user credentials were stored in plain text in memory snapshots

  • Medium 5.4

    In JetBrains TeamCity before 2025.07 a CSRF was possible on GraphQL endpoint

  • Medium 5.8

    In JetBrains TeamCity before 2025.07 password reset and email verification tokens were using weak hashing algorithms

  • Medium 4.3

    In JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via VCS configuration

  • Medium 4.8

    In JetBrains TeamCity before 2025.07 reflected XSS was possible on the agentpushPreset page

  • Medium 4.3

    In JetBrains TeamCity before 2025.07 improper access control allowed disclosure of build settings via snapshot dependen…

  • Medium 5.4

    In JetBrains TeamCity before 2025.07 a CSRF was possible in GitHub App connection flow

  • Medium 4.3

    In JetBrains TeamCity before 2025.03.3 usernames were exposed to the users without proper permissions

  • Medium 4.8

    In JetBrains TeamCity before 2025.03.3 reflected XSS in the NPM Registry integration was possible

  • Medium 5.4
    CVE-2025-52876 EPSS 39%

    In JetBrains TeamCity before 2025.03.3 reflected XSS on the favoriteIcon page was possible

  • Medium 4.8
    CVE-2025-52877 EPSS 37%

    In JetBrains TeamCity before 2025.03.3 reflected XSS on diskUsageBuildsStats page was possible

  • Medium 5.4

    In JetBrains TeamCity before 2025.03.3 a DOM-based XSS at the Performance Monitor page was possible

  • Medium 4.3

    In JetBrains TeamCity before 2025.03.2 open redirect was possible on editing VCS Root page

  • Medium 4.8

    In JetBrains TeamCity before 2025.03.2 stored XSS via Jira integration was possible

  • Medium 4.8

    In JetBrains TeamCity before 2025.03.2 stored XSS via YouTrack integration was possible

  • Medium 4.8

    In JetBrains TeamCity before 2025.03.2 stored XSS via GitHub Checks Webhook was possible

  • Medium 4.3

    In JetBrains TeamCity before 2025.03.1 base64-encoded credentials could be exposed in build logs

  • Medium 4.9

    In JetBrains TeamCity before 2025.03.1 improper path validation in loggingPreset parameter was possible

  • Medium 4.6
    CVE-2025-31140 EPSS 28%

    In JetBrains TeamCity before 2025.03 stored XSS was possible on Cloud Profiles page

  • Medium 4.3

    In JetBrains TeamCity before 2025.03 base64 encoded password could be exposed in build log

  • Medium 4.6

    In JetBrains TeamCity before 2024.12.2 several DOM-based XSS were possible on the Code Inspection Report tab