dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-46432

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-25
Fix available
A fix is available. Upgrade to 2025.03.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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.03.1 base64-encoded credentials could be exposed in build logs

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 · high confidence

In JetBrains TeamCity versions prior to 2025.03.1, base64-encoded credentials were being written to build logs. While base64 encoding provides no security (it is easily reversible), this still allowed anyone with access to build logs to obtain credentials used during build processes.

MitigationUpgrade TeamCity to version 2025.03.1 or later. As a precaution, rotate any credentials that may have been exposed in build logs.

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

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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
    Access the TeamCity administration UI and navigate to 'About' or check the server startup logs for the version number. Alternatively, query the TeamCity REST API at /app/rest/server/version or check the teamcity-server.log file for the version string.
    Affected if The version is lower than 2025.03.1 (e.g., 2024.x, 2023.x, etc.)
  2. Search build logs for base64-encoded strings
    Use TeamCity's log viewer or access the build logs directory (typically under /logs or /data/system/builds) and search for base64 patterns. Look for long alphanumeric strings (typically 20+ characters) that appear in lines related to authentication, credential usage, or environment variable setting.
    Affected if Build logs contain base64 strings that decode to sensitive values like passwords, API keys, tokens, or connection strings.
  3. Review build configurations for credential usage
    Examine build configurations in TeamCity that use password/credential parameters, especially in build steps, environment variables, or artifact paths. Check the 'Parameters' section of build configurations for any parameters marked as password or secured.
    Affected if Build configurations use secured or password-type parameters and the build logs show base64 activity related to those parameters.
  4. Inspect build agent logs
    Check build agent logs for any base64-encoded credential transmission or usage. These logs are typically found in the agent's work directory or logs folder.
    Affected if Agent logs show base64 strings being passed during build execution.

You are affected if your TeamCity version is below 2025.03.1 AND your build logs contain base64-encoded strings that correspond to credentials used in build processes.

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.03.1 or later
Fixed in 2025.03.1
Interim mitigation

Upgrade TeamCity to version 2025.03.1 or later. As a precaution, rotate any credentials that may have been exposed in build logs.

Recommended fix High confidence

TeamCity 2025.03.1

  1. Backup your current TeamCity installation and database
  2. Download TeamCity version 2025.03.1 from the official JetBrains website (www.jetbrains.com)
  3. Stop the TeamCity server
  4. Follow the standard TeamCity upgrade procedure for your installation method
  5. Start the TeamCity server after upgrade completes
  6. Verify the upgrade was successful by checking the TeamCity version
  7. Confirm that credentials are no longer exposed in build logs

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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