In JetBrains TeamCity before 2026.2.2, 2026.1.6 a CSRF attack was possible on the Hub integration settings
Source GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 2026.2.2 or 2026.1.6 soon.
Data as of 19 Nov 2026, 16:40 UTC
Thin evidence
One scorer or none| CNA (JetBrains) | CVSS 3.1 | 8.1 |
|---|
- Patch
- Available – fixed in 2026.2.2, 2026.1.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 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 and org.jetbrains.teamcity/teamcity-server to 2026.2.2 or 2026.1.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JetBrainsTeamCity | Affected
| Fixed in
|
| JetBrainsTeamCity | Affected
| Fixed in
|
Mavenorg.jetbrains.teamcity/teamcity-serverpkg:maven/org.jetbrains.teamcity/teamcity-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade JetBrains TeamCity to versions 2026.2.2 or 2026.1.6 or later where this CSRF vulnerability is fixed. Since the vendor advisory or patch links are not provided, confirm the availability of these fixed versions from official JetBrains sources before upgrading. Until patched, users should consider restricting access to the Hub integration settings and applying standard CSRF protections if possible.
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in JetBrains TeamCity versions prior to 2026.2.2 and 2026.1.6, specifically affecting the Hub integration settings. This vulnerability allows an attacker to perform unauthorized actions via forged requests. The vulnerability has a high severity score of 8.1 but no known exploits in the wild have been reported.