CVE-2026-28196: JetBrains TeamCity · CWE-459
Affects JetBrains TeamCitySource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 2025.11.3 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2025.11.3
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Feb 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 29 Oct 2026.
What to do
Upgrade JetBrains TeamCity to 2025.11.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JetBrainsTeamCity | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-28196, organizations should upgrade JetBrains TeamCity to version 2025.11.3 or later, where this issue is addressed. If you cannot patch yet, administrators should audit their TeamCity configurations to ensure versioned settings are enabled or verify that credentials files are securely managed and removed when no longer needed. Restrict local access to build servers to trusted personnel only and enforce strict file system permissions to prevent unauthorized reading of configuration files. Implement monitoring to detect unusual access patterns to sensitive files. Additionally, consider encrypting credentials at rest and using secure vault solutions integrated with TeamCity to avoid storing plaintext credentials on disk. Regularly review and rotate credentials used within CI/CD pipelines to minimize the impact of potential exposure. Finally, maintain a robust incident response plan to quickly address any detected credential leaks or unauthorized access.
Description
In JetBrains TeamCity before 2025.11.3 disabling versioned settings left a credentials config on disk