Skip to content
OpenAdvisories

Product · JetBrains

TeamCity

191 known vulnerabilities.

TeamCity at a glance

Last 12 months
41
Critical · all time
6
Exploited · all time
4
Public exploit · all time
5

4 of the exploited vulnerabilities are known to be used by ransomware (CISA).

New vulnerabilities per month · last 12 months
0 10 20 December 2025: 11 vulnerabilities Dec 2025 January 2026: 0 vulnerabilities February 2026: 3 vulnerabilities March 2026: 0 vulnerabilities Mar April 2026: 0 vulnerabilities May 2026: 12 vulnerabilities June 2026: 0 vulnerabilities Jun July 2026: 7 vulnerabilities, 2 critical August 2026: 0 vulnerabilities September 2026: 3 vulnerabilities Sep October 2026: 5 vulnerabilities November 2026: 0 vulnerabilities
Show as table
MonthVulnerabilitiesCritical
Nov 202600
Oct 202650
Sep 202630
Aug 202600
Jul 202672
Jun 202600
May 2026120
Apr 202600
Mar 202600
Feb 202630
Jan 202600
Dec 2025110
Nov 202500
Oct 202500
Sep 202530
Aug 202530
Jul 2025110
Jun 202550
May 202540
Apr 202530
Mar 202530
Feb 202520
Jan 202530
Dec 202490

Latest advisories

  • High max 8.1

    JetBrains TeamCity: Mehrere Schwachstellen

    Ein Angreifer kann mehrere Schwachstellen in JetBrains TeamCity ausnutzen, um beliebigen Programmcode auszuführen, und um einen Cross-Site Scripting Angriff durchzuführen.

  • High max 8.8

    JetBrains TeamCity: Mehrere Schwachstellen

    Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in JetBrains TeamCity ausnutzen, um beliebigen Programmcode auszuführen und Informationen offenzulegen.

  • High max 8.8

    JetBrains TeamCity: Mehrere Schwachstellen

    Ein Angreifer kann mehrere Schwachstellen in JetBrains TeamCity ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen und Administratorrechte zu erlangen.

  • Critical max 9.8
    WID-SEC-2026-2534 1 CVE 1 exploited rev. 3

    JetBrains TeamCity: Schwachstelle ermöglicht Codeausführung

    Ein entfernter, anonymer Angreifer kann eine Schwachstelle in JetBrains TeamCity ausnutzen, um beliebigen Programmcode auszuführen.

    first Jul 27, 2026
  • High max 9.1

    JetBrains TeamCity: Mehrere Schwachstellen ermöglichen Codeausführung

    Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in JetBrains TeamCity ausnutzen, um beliebigen Programmcode auszuführen.

191 results · 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

  • 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

  • Medium 6.5

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

  • 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 …

  • Critical 9.8
    CVE-2026-63077 Exploited · Ransomware Public exploit Scanner template EPSS 95%

    In JetBrains TeamCity before 2026.1.3, 2025.11.7 unauthenticated remote code execution was possible via the agent polli…

    KEV Aug 5, 2026
  • Critical 9.1

    In JetBrains TeamCity before 2026.1.2, 2025.11.6 code execution in Git VCS roots was possible

  • 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.1
    CVE-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

  • 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

  • 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

  • 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.1
    CVE-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

  • Low 2.3

    In JetBrains TeamCity before 2025.11.3 disabling versioned settings left a credentials config on disk

  • 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

  • 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

  • Medium 4.8

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

  • Low 2.7

    In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata