dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-59457

HIGH · 7.7 CVSS v3.1 Published 2025-09-17
Fix available
A fix is available. Upgrade to 2025.07.2 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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.2 missing Git URL validation allowed credential leakage on Windows

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

In JetBrains TeamCity versions prior to 2025.07.2, insufficient validation of Git repository URLs allowed credential leakage when Windows agents connected to malicious or compromised Git repositories. The vulnerability stems from improper sanitization of Git URLs, potentially exposing stored credentials during repository operations.

MitigationUpgrade TeamCity to version 2025.07.2 or later to obtain the validated Git URL handling. Review existing Git configurations and rotate any credentials that may have been exposed before the patch was applied.

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.2

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

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

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 installed TeamCity version
    Check the TeamCity server interface: go to Administration > Server Administration > Server Information, or access /admin/admin.html?item=server on the TeamCity server. The version is displayed on that page.
    Affected if The installed version is any release earlier than 2025.07.2
  2. Verify if Git is used as a version control provider
    In TeamCity, navigate to Administration > Version Control Settings to see configured VCS roots. Look for VCS roots using the Git type.
    Affected if Git VCS roots are configured and the TeamCity version is below 2025.07.2
  3. Confirm presence of Windows build agents
    In TeamCity, go to Administration > Agents. Review the agent pool to identify any agents running Windows operating systems.
    Affected if Windows agents are connected and the TeamCity version is below 2025.07.2 with Git VCS roots configured
  4. Review Git credential storage configuration
    In TeamCity, go to Administration > Server Administration > Global Settings or check individual VCS root settings to see how credentials (HTTPS username/password, SSH keys, or token-based authentication) are stored for Git repositories.
    Affected if Git credentials are stored in TeamCity and the version is below 2025.07.2

The environment is affected if TeamCity version is below 2025.07.2, Git repositories are configured, and Windows build agents are used, as this combination enables the credential leakage vulnerability through improper Git URL validation.

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.2 or later
Fixed in 2025.07.2
Interim mitigation

Upgrade TeamCity to version 2025.07.2 or later to obtain the validated Git URL handling. Review existing Git configurations and rotate any credentials that may have been exposed before the patch was applied.

Recommended fix High confidence

TeamCity 2025.07.2 or later

  1. 1. Back up the TeamCity server data directory and database before upgrading
  2. 2. Download TeamCity 2025.07.2 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the running TeamCity server service
  4. 4. Install or deploy the new TeamCity version following standard upgrade procedures
  5. 5. Start the TeamCity server and verify it runs correctly
  6. 6. Confirm the Git URL validation fix is applied by testing Git repository connections
Caveat Review TeamCity 2025.07.2 release notes for any configuration or feature changes; point releases typically have minimal breaking changes

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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