CVE-2025-59455: JetBrains TeamCity · Race Condition
Affects JetBrains TeamCitySource CVE Database V5
Not known to be exploited · CVSS 4.2 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 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
European organizations should prioritize upgrading JetBrains TeamCity installations to version 2025.07.2 or later as soon as the patch becomes available. In the interim, organizations should enforce strict access controls to limit the number of users with project-level privileges, minimizing the attack surface. Implementing robust monitoring and alerting for unusual access patterns or race condition exploitation attempts can help detect potential attacks early. Additionally, organizations should review and harden their CI/CD pipeline security policies, including segregating projects and enforcing the principle of least privilege. Employing network segmentation to restrict access to TeamCity servers and using multi-factor authentication for all users with elevated privileges can further reduce risk. Regular security audits and penetration testing focused on race conditions and access control bypasses in CI/CD environments are recommended to proactively identify and remediate similar vulnerabilities.
Description
In JetBrains TeamCity before 2025.07.2 project isolation bypass was possible due to race condition