TeamCity
JetBrains- Product type
- Other
- Catalog vulnerabilities
- 276
Severity across 100 analyzed records
en
Verify to analyze this security profile
As of 09/13/2026, within CyStack's analyzed data, TeamCity has 7 security vulnerabilities published in the last 90 days. Of these, 7 are rated High or Critical. Notably, 1 of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of TeamCity and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-63077 | Exploitation statusKEV | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-65907 | Exploitation statusNot known exploited | FixYes | Published07/23/2026 | SeverityCritical |
CVE-2026-65906 | Exploitation statusNot known exploited | FixYes | Published07/23/2026 | SeverityHigh |
CVE-2026-59796 | Exploitation statusNot known exploited | FixYes | Published07/10/2026 | SeverityHigh |
CVE-2026-59795 | Exploitation statusNot known exploited | FixYes | Published07/10/2026 | SeverityHigh |
CVE-2026-59794 | Exploitation statusNot known exploited | FixYes | Published07/10/2026 | SeverityHigh |
CVE-2026-59793 | Exploitation statusNot known exploited | FixYes | Published07/10/2026 | SeverityHigh |
CVE-2026-49381 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityLow |
CVE-2026-49380 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityLow |
CVE-2026-49379 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityMedium |
CVE-2026-49378 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityMedium |
CVE-2026-49377 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityMedium |
CVE-2026-49376 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityMedium |
CVE-2026-49375 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityMedium |
CVE-2026-49374 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityHigh |
CVE-2026-49373 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityHigh |
CVE-2026-49372 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityHigh |
CVE-2026-49371 | Exploitation statusNot known exploited | FixYes | Published05/29/2026 | SeverityHigh |
CVE-2026-44413 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28196 | Exploitation statusNot known exploited | FixYes | Published02/25/2026 | SeverityLow |
CVE-2026-28195 | Exploitation statusNot known exploited | FixYes | Published02/25/2026 | SeverityMedium |
CVE-2026-28194 | Exploitation statusNot known exploited | FixYes | Published02/25/2026 | SeverityMedium |
CVE-2025-68268 | Exploitation statusNot known exploited | FixYes | Published12/16/2025 | SeverityMedium |
CVE-2025-68267 | Exploitation statusNot known exploited | FixYes | Published12/16/2025 | SeverityMedium |
CVE-2025-68166 | Exploitation statusNot known exploited | FixYes | Published12/16/2025 | SeverityMedium |
CVE-2025-68165 | Exploitation statusNot known exploited | FixYes | Published12/16/2025 | SeverityMedium |
CVE-2025-68164 | Exploitation statusNot known exploited | FixYes | Published12/16/2025 | SeverityLow |
CVE-2025-68163 | Exploitation statusNot known exploited | FixYes | Published12/16/2025 | SeverityLow |
CVE-2025-68162 | Exploitation statusNot known exploited | FixYes | Published12/16/2025 | SeverityLow |
CVE-2025-67742 | Exploitation statusNot known exploited | FixYes | Published12/11/2025 | SeverityLow |
CVE-2025-67741 | Exploitation statusNot known exploited | FixYes | Published12/11/2025 | SeverityMedium |
CVE-2025-67740 | Exploitation statusNot known exploited | FixYes | Published12/11/2025 | SeverityLow |
CVE-2025-67739 | Exploitation statusNot known exploited | FixYes | Published12/11/2025 | SeverityLow |
CVE-2025-59457 | Exploitation statusNot known exploited | FixYes | Published09/17/2025 | SeverityHigh |
CVE-2025-59456 | Exploitation statusNot known exploited | FixYes | Published09/17/2025 | SeverityMedium |
CVE-2025-59455 | Exploitation statusNot known exploited | FixYes | Published09/17/2025 | SeverityMedium |
CVE-2025-57734 | Exploitation statusNot known exploited | FixYes | Published08/20/2025 | SeverityMedium |
CVE-2025-57733 | Exploitation statusNot known exploited | FixYes | Published08/20/2025 | SeverityMedium |
CVE-2025-57732 | Exploitation statusNot known exploited | FixYes | Published08/20/2025 | SeverityHigh |
CVE-2025-54538 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-54537 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-54536 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-54535 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-54534 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-54533 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-54532 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-54531 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityHigh |
CVE-2025-54530 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityHigh |
CVE-2025-54529 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityLow |
CVE-2025-54528 | Exploitation statusNot known exploited | FixYes | Published07/28/2025 | SeverityMedium |
CVE-2025-52879 | Exploitation statusNot known exploited | FixYes | Published06/23/2025 | SeverityMedium |
CVE-2025-52878 | Exploitation statusNot known exploited | FixYes | Published06/23/2025 | SeverityMedium |
CVE-2025-52877 | Exploitation statusNot known exploited | FixYes | Published06/23/2025 | SeverityMedium |
CVE-2025-52876 | Exploitation statusNot known exploited | FixYes | Published06/23/2025 | SeverityMedium |
CVE-2025-52875 | Exploitation statusNot known exploited | FixYes | Published06/23/2025 | SeverityMedium |
CVE-2025-47854 | Exploitation statusNot known exploited | FixYes | Published05/20/2025 | SeverityMedium |
CVE-2025-47853 | Exploitation statusNot known exploited | FixYes | Published05/20/2025 | SeverityMedium |
CVE-2025-47852 | Exploitation statusNot known exploited | FixYes | Published05/20/2025 | SeverityMedium |
CVE-2025-47851 | Exploitation statusNot known exploited | FixYes | Published05/20/2025 | SeverityMedium |
CVE-2025-46618 | Exploitation statusNot known exploited | FixYes | Published04/25/2025 | SeverityLow |
CVE-2025-46433 | Exploitation statusNot known exploited | FixYes | Published04/25/2025 | SeverityMedium |
CVE-2025-46432 | Exploitation statusNot known exploited | FixYes | Published04/25/2025 | SeverityMedium |
CVE-2025-31141 | Exploitation statusNot known exploited | FixYes | Published03/27/2025 | SeverityLow |
CVE-2025-31140 | Exploitation statusNot known exploited | FixYes | Published03/27/2025 | SeverityMedium |
CVE-2025-31139 | Exploitation statusNot known exploited | FixYes | Published03/27/2025 | SeverityMedium |
CVE-2025-26492 | Exploitation statusNot known exploited | FixYes | Published02/11/2025 | SeverityHigh |
CVE-2025-26493 | Exploitation statusNot known exploited | FixYes | Published02/11/2025 | SeverityMedium |
CVE-2025-24461 | Exploitation statusNot known exploited | FixYes | Published01/21/2025 | SeverityMedium |
CVE-2025-24460 | Exploitation statusNot known exploited | FixYes | Published01/21/2025 | SeverityMedium |
CVE-2025-24459 | Exploitation statusNot known exploited | FixYes | Published01/21/2025 | SeverityMedium |
CVE-2024-56356 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56355 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56354 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56353 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56352 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56351 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56350 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56349 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-56348 | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityMedium |
CVE-2024-47951 | Exploitation statusNot known exploited | FixYes | Published10/08/2024 | SeverityLow |
CVE-2024-47950 | Exploitation statusNot known exploited | FixYes | Published10/08/2024 | SeverityLow |
CVE-2024-47949 | Exploitation statusNot known exploited | FixYes | Published10/08/2024 | SeverityMedium |
CVE-2024-47948 | Exploitation statusNot known exploited | FixYes | Published10/08/2024 | SeverityMedium |
CVE-2024-47161 | Exploitation statusNot known exploited | FixYes | Published10/08/2024 | SeverityMedium |
CVE-2024-43810 | Exploitation statusNot known exploited | FixYes | Published08/16/2024 | SeverityMedium |
CVE-2024-43809 | Exploitation statusNot known exploited | FixYes | Published08/16/2024 | SeverityLow |
CVE-2024-43808 | Exploitation statusNot known exploited | FixYes | Published08/16/2024 | SeverityLow |
CVE-2024-43807 | Exploitation statusNot known exploited | FixYes | Published08/16/2024 | SeverityMedium |
CVE-2024-43114 | Exploitation statusNot known exploited | FixYes | Published08/06/2024 | SeverityHigh |
CVE-2024-41829 | Exploitation statusNot known exploited | FixYes | Published07/22/2024 | SeverityLow |
CVE-2024-41828 | Exploitation statusNot known exploited | FixYes | Published07/22/2024 | SeverityLow |
CVE-2024-41827 | Exploitation statusNot known exploited | FixYes | Published07/22/2024 | SeverityHigh |
CVE-2024-41826 | Exploitation statusNot known exploited | FixYes | Published07/22/2024 | SeverityLow |
CVE-2024-41825 | Exploitation statusNot known exploited | FixYes | Published07/22/2024 | SeverityMedium |
CVE-2024-41824 | Exploitation statusNot known exploited | FixYes | Published07/22/2024 | SeverityMedium |
CVE-2024-39879 | Exploitation statusNot known exploited | FixYes | Published07/01/2024 | SeverityMedium |
CVE-2024-39878 | Exploitation statusNot known exploited | FixYes | Published07/01/2024 | SeverityMedium |
CVE-2024-36470 | Exploitation statusNot known exploited | FixYes | Published05/29/2024 | SeverityHigh |
CVE-2024-36378 | Exploitation statusNot known exploited | FixYes | Published05/29/2024 | SeverityMedium |
CVE-2024-36377 | Exploitation statusNot known exploited | FixYes | Published05/29/2024 | SeverityMedium |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan