JetBrains TeamCity: Mehrere Schwachstellen
Affects Bundesamt für Sicherheit in der Informationstechnik JetBrainsSource GCVE Database
Not known to be exploited · CVSS 9.9 Critical : upgrade to 2026.1.3 or 2025.11.7 as a priority.
Data as of 19 Nov 2026, 12:07 UTC
Thin evidence
One scorer or none| CNA (JetBrains) | CVSS 3.1 | 9.9 |
|---|
- Patch
- Available – fixed in 2026.1.3, 2025.11.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade TeamCity to 2026.1.3 or 2025.11.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JetBrainsTeamCity | Affected
| Fixed in
|
| JetBrainsTeamCity | Affected
| Fixed in
|
AI-suggested
Users should upgrade to JetBrains TeamCity version 2026.1.3 or later, as this version contains fixes for the reported vulnerabilities. No additional mitigation steps are indicated.
Description
Multiple vulnerabilities have been identified in JetBrains TeamCity, a Continuous Integration and Deployment tool used by developers and DevOps engineers. These issues affect versions prior to 2026.1.3 and the version 2026.1.3 itself. A fixed version, 2026.1.3, is available to address these vulnerabilities.
References
- wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-4661.json (opens in a new tab)
- wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4661 (opens in a new tab)
- jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132231 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132232 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132233 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132234 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132235 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132236 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132237 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132238 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132239 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132240 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132241 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132242 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132243 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132244 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132245 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132246 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-132247 (opens in a new tab)