In JetBrains TeamCity before 2026.1.3, 2025.11.7 missing authorization in the Kubernetes integration allowed project
Source GCVE Database
Not known to be exploited · CVSS 7.6 High : upgrade to 2026.1.3 or 2025.11.7 soon.
Data as of 18 Nov 2026, 20:05 UTC
Thin evidence
One scorer or none| CNA (JetBrains) | CVSS 3.1 | 7.6 |
|---|
- Patch
- Available – fixed in 2026.1.3, 2025.11.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 17 Nov 2026.
What to do
Upgrade TeamCity and org.jetbrains.teamcity/teamcity-server to 2026.1.3 or 2025.11.7.
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
A fix is available in JetBrains TeamCity versions 2026.1.3 and 2025.11.7. Users should upgrade to these or later versions to remediate the vulnerability. Since no vendor advisory or patch links are provided, confirm patch availability and upgrade instructions from JetBrains official sources before applying.
Description
A missing authorization vulnerability in the Kubernetes integration of JetBrains TeamCity before versions 2026.1.3 and 2025.11.7 allows project viewers to access and use stored credentials. This flaw could lead to unauthorized use of credentials within the affected TeamCity instances.