JetBrains TeamCity vulnerabilities and fixes
CVEs that mention JetBrains TeamCity, ranked by priority. 3 tracked.
JetBrains TeamCity has 3 tracked vulnerabilities, 2 critical and 1 exploited in the wild (CISA KEV). A fixed release or vendor patch exists for 3. Most recent: 2026-07-27. Highest priority: CVE-2026-63077 (score 100/100).
- CVE-2026-63077 CRITICAL 9.8 EXPLOITED UPGRADE JetBrains TeamCity Deserialization of Untrusted Data Vulnerability
- CVE-2026-65907 CRITICAL 9.1 In JetBrains TeamCity before 2026.1.2, 2025.11.6 code execution in Git VCS roots was possible
- CVE-2026-65906 HIGH 8.8 UPGRADE In JetBrains TeamCity before 2026.1.2, 2025.11.6 сode execution via Kotlin DSL sandbox escape was possible
FAQ
How do I fix JetBrains TeamCity vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is JetBrains TeamCity being exploited right now?
Yes: 1 JetBrains TeamCity CVE is on the CISA Known Exploited Vulnerabilities list, so patch it first.
Which JetBrains TeamCity CVE should I patch first?
CVE-2026-63077 currently ranks highest (100/100): JetBrains TeamCity Deserialization of Untrusted Data Vulnerability.
Newest JetBrains TeamCity CVEs
- CVE-2026-63077 CRITICAL 9.8 2026-07-27: JetBrains TeamCity Deserialization of Untrusted Data Vulnerability
- CVE-2026-65907 CRITICAL 9.1 2026-07-23: In JetBrains TeamCity before 2026.1.2, 2025.11.6 code execution in Git VCS roots was possi
- CVE-2026-65906 HIGH 8.8 2026-07-23: In JetBrains TeamCity before 2026.1.2, 2025.11.6 сode execution via Kotlin DSL sandbox esc
Live from the NVD (last 120 days)
Loading…