CVE-2025-54538: JetBrains TeamCity · CWE-312
Affects JetBrains TeamCitySource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 08:11 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JetBrains TeamCity | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should include restricting local access to build servers running TeamCity to trusted personnel only, minimizing the risk of unauthorized process inspection. 2. Configure TeamCity and Mercurial integrations to avoid passing passwords via command line arguments; instead, use secure credential storage mechanisms such as environment variables, credential helpers, or encrypted configuration files. 3. Monitor and audit process listings and command histories on build servers for any exposure of sensitive information. 4. Implement strict access controls and logging on build infrastructure to detect and respond to suspicious activities promptly. 5. Encourage the use of dedicated service accounts with minimal privileges for build operations to limit potential damage from credential exposure. 6. Once JetBrains releases an official patch or update addressing this vulnerability, prioritize applying it in all affected environments. 7. Educate developers and DevOps teams about the risks of exposing credentials in command lines and promote best practices for secret management. 8. Consider isolating build environments or using containerization to reduce the attack surface for local privilege escalation or credential theft.
Description
In JetBrains TeamCity before 2025.07 password exposure was possible via command line in the "hg pull" command