CVE-2025-31139
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 · uneditedIn JetBrains TeamCity before 2025.03 base64 encoded password could be exposed in build log
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 confidenceIn JetBrains TeamCity versions prior to 2025.03, base64 encoded passwords were being written to build logs during build processes. While base64 encoding is not encryption, it provides no security and the encoded passwords can be trivially decoded, exposing plaintext credentials to anyone with access to the 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< 2025.03CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine your TeamCity versionAccess the TeamCity administration interface and navigate to 'About TeamCity' or check the server startup logs for the version numberAffected if The installed version is earlier than 2025.03
-
Review recent build logs for base64 stringsExamine build logs from the Build Results page, looking for long alphanumeric strings (typically 20+ characters) that appear in password-related parameters or environment variablesAffected if Build logs contain base64 encoded strings that decode to plaintext passwords or secrets
-
Check for password-type build parameters in logsInspect build configuration parameters and build log output for entries containing 'password', 'pwd', 'secret', 'token', or 'credential' that contain base64-encoded valuesAffected if Password or credential parameters are being printed to the build log in base64 form
-
Examine build step output for sensitive parametersLook at the raw build log output for any build steps that pass passwords as command-line arguments or environment variablesAffected if Build steps expose password values (even when base64 encoded) in the visible log output
-
Check VCS roots and secure settingsReview VCS root configurations and other secure settings stored in TeamCity for any that may have been loggedAffected if Credentials stored in VCS roots or secure configurations appeared in build logs
You are affected if your TeamCity version is before 2025.03 AND base64-encoded password strings appear in any build logs or build configuration outputs.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2025.03
Upgrade to TeamCity 2025.03 or later to prevent password leakage in logs. Additionally, rotate any credentials that may have been exposed in build logs as a precautionary measure.
TeamCity 2025.03
- Plan and schedule the TeamCity upgrade to minimize disruption to build processes
- Take a complete backup of the TeamCity database and configuration files
- Download TeamCity 2025.03 from the official JetBrains website (www.jetbrains.com)
- Follow the standard TeamCity upgrade procedure (stop the server, run the installer or replace the installation files, start the server)
- After upgrade, verify that build logs no longer contain base64 encoded passwords
- Review build logs to confirm the sensitive information exposure has been resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-31139 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31139 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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