dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-54529

HIGH · 7.5 CVSS v3.1 Published 2025-07-28
Fix available
A fix is available. Upgrade to 2025.07 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In JetBrains TeamCity before 2025.07 a CSRF was possible in external OAuth login integration

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A CSRF (Cross-Site Request Forgery) vulnerability in JetBrains TeamCity's external OAuth login integration allows attackers to potentially craft malicious requests that trick authenticated users into performing unintended OAuth-related actions. The flaw exists in versions prior to 2025.07.

MitigationUpgrade JetBrains TeamCity to version 2025.07 or later, which includes the CSRF protection fix for the external OAuth login flow. After upgrading, verify OAuth authentication still functions correctly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TeamcityApplication
Affected:< 2025.07

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify TeamCity installation
    Locate TeamCity installation directory, typically found under /opt/teamcity, C:\Program Files\JetBrains\TeamCity, or /usr/local/teamcity on Linux systems. Check for the TeamCity server process running on port 8111 by default.
    Affected if TeamCity is installed and accessible
  2. Determine installed TeamCity version
    Check the version by viewing the buildServerConfig\buildServer.properties file (Windows) or /opt/teamcity/conf/buildServer.properties (Linux), looking for the version number in the UI at /about.html, or using the command: curl -s http://localhost:8111/rest/server/version
    Affected if Version is lower than 2025.07
  3. Check if external OAuth providers are configured
    Examine the <TeamCity data directory>/config/oauth-providers.xml or the internal database for OAuth provider configurations. In the TeamCity UI, navigate to Administration > Authentication Settings to see if external OAuth providers (such as Google, GitHub, GitLab, Azure AD, etc.) are enabled.
    Affected if One or more external OAuth login providers are configured and enabled
  4. Inspect OAuth callback endpoint configuration
    Verify the OAuth callback URL is publicly accessible. Check the teamcity-authentication.xml or equivalent configuration files in <TeamCity data directory>/config for OAuth-related settings. Look for endpoints matching /oauth2/login/* or /extlogin/oauth* patterns.
    Affected if External OAuth login endpoints are exposed without additional CSRF protection tokens

You are affected if running TeamCity version below 2025.07 AND external OAuth providers are configured for user authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.07 or later
Fixed in 2025.07
Interim mitigation

Upgrade JetBrains TeamCity to version 2025.07 or later, which includes the CSRF protection fix for the external OAuth login flow. After upgrading, verify OAuth authentication still functions correctly.

Recommended fix High confidence

2025.07

  1. 1. Create a full backup of the TeamCity data directory (by default <TeamCity home>/data)
  2. 2. Download TeamCity version 2025.07 from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the TeamCity server gracefully
  4. 4. Install the new version following the standard upgrade procedure (run the installer or extract the distribution package)
  5. 5. Start the TeamCity server and verify all services are running
  6. 6. Test the external OAuth login integration to confirm the CSRF fix is working
  7. 7. Review the TeamCity 2025.07 release notes for any additional configuration requirements
Caveat Review release notes for potential breaking changes; standard upgrade precautions apply (backup before upgrading)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54529 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54529 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data