In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings
Source GCVE Database
Not known to be exploited · CVSS 8.8 High : upgrade to 2026.2.2 or 2026.1.6 soon.
Data as of 19 Nov 2026, 17:04 UTC
Thin evidence
One scorer or none| CNA (JetBrains) | CVSS 3.1 | 8.8 |
|---|
- Patch
- Available – fixed in 2026.2.2, 2026.1.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation 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 to 2026.2.2 or 2026.1.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JetBrainsTeamCity | Affected
| Fixed in
|
| JetBrainsTeamCity | Affected
| Fixed in
|
AI-suggested
Upgrade JetBrains TeamCity to version 2026.2.2 or 2026.1.6 or later, where this vulnerability is fixed. Since this is an on-premises product, applying the official vendor patch is required to remediate the issue. No other mitigation or workaround is indicated in the available data.
Description
A remote code execution vulnerability exists in JetBrains TeamCity versions before 2026.2.2 and 2026.1.6. The flaw is triggered via Maven repository settings, allowing an attacker with limited privileges to execute arbitrary code remotely. This vulnerability has a high severity rating with a CVSS score of 8.8.