CVE-2025-54529: JetBrains TeamCity · Cross-Site Request Forgery
Affects JetBrains TeamCitySource CVE Database V5
Not known to be exploited · CVSS 3.7 Low.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JetBrains TeamCity | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability effectively, European organizations should: 1) Immediately upgrade JetBrains TeamCity to version 2025.07 or later once the patch is officially released, as this version addresses the CSRF issue in OAuth login integration. 2) Until patching is possible, restrict access to the TeamCity server to trusted networks and users, minimizing exposure to potential attackers. 3) Implement strict Content Security Policy (CSP) headers and SameSite cookie attributes to reduce the risk of CSRF attacks. 4) Review and harden OAuth integration configurations, ensuring that redirect URIs and state parameters are properly validated to prevent unauthorized OAuth flows. 5) Educate users, especially those with build administration privileges, about the risks of clicking on suspicious links while authenticated to TeamCity. 6) Monitor TeamCity logs for unusual activities such as unexpected build triggers or configuration changes that could indicate exploitation attempts. 7) Consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block CSRF attack patterns targeting the TeamCity OAuth endpoints. These targeted measures go beyond generic advice by focusing on the specific OAuth integration vector and build system context.
Description
In JetBrains TeamCity before 2025.07 a CSRF was possible in external OAuth login integration