dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-54528

HIGH · 8.8 CVSS v3.1 Published 2025-07-28
Fix available
A fix is available. Upgrade to 2025.07 or later.
See remediation →
95/100
Remediation priority · Urgent
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 GitHub App connection flow

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 existed in the GitHub App connection flow of JetBrains TeamCity versions prior to 2025.07. This flaw could allow attackers to trick authenticated users into unknowingly performing unwanted actions in the GitHub App integration, such as modifying or disconnecting connections.

MitigationUpgrade to TeamCity version 2025.07 or later, which contains the fix for this CSRF vulnerability in the GitHub App connection flow.

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Determine installed TeamCity version
    Access the TeamCity administration UI and navigate to 'Administration' > 'Server Administration' > 'Server Information' to view the exact version number. Alternatively, check the version.txt file in the TeamCity installation directory.
    Affected if The installed version is earlier than 2025.07 (e.g., 2025.06, 2025.05, 2024.x, etc.)
  2. Verify if GitHub App integration is configured
    Navigate to 'Administration' > 'Integrations' > 'GitHub' in the TeamCity web UI. Check if any GitHub App connections are listed or if the 'GitHub Apps' tab shows configured integrations.
    Affected if A GitHub App connection is configured and active in TeamCity; the vulnerability exists specifically in the GitHub App connection flow
  3. Inspect CSRF protection configuration
    Check the TeamCity main configuration file (usually <TeamCity_home>/conf/server.xml or via the administration UI under 'Administration' > 'Global Settings') for CSRF token enforcement settings. Look for 'csrf' or 'token' related security parameters.
    Affected if CSRF protection is disabled, not properly enforced, or using default/weak token configuration
  4. Review GitHub integration audit logs
    Access TeamCity audit logs via 'Administration' > 'Audit' or check the logs directory for entries related to GitHub connections. Look for unexpected or unauthorized modifications to GitHub App settings.
    Affected if Unexpected changes to GitHub integration settings appear in logs, or connection modifications were made by users who did not intentionally configure them

You are affected if your TeamCity version is earlier than 2025.07 AND you have GitHub App integrations configured, as the CSRF vulnerability in the GitHub App connection flow could allow unauthorized modifications to your GitHub integrations.

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 to TeamCity version 2025.07 or later, which contains the fix for this CSRF vulnerability in the GitHub App connection flow.

Recommended fix High confidence

2025.07

  1. 1. Back up your existing TeamCity database and configuration files
  2. 2. Download TeamCity 2025.07 from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the running TeamCity server
  4. 4. Install the new version following the standard TeamCity upgrade documentation
  5. 5. Start the TeamCity server and verify all services are running
  6. 6. Test the GitHub App connection flow to confirm the CSRF vulnerability is resolved
  7. 7. Review the TeamCity 2025.07 release notes for any configuration changes needed

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54528 — 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-54528 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