CVE-2025-54535
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.07 password reset and email verification tokens were using weak hashing algorithms
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 before 2025.07, password reset and email verification tokens were hashed using weak cryptographic algorithms, potentially allowing attackers to crack or predict tokens and achieve unauthorized account takeover.
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.07CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate your TeamCity version numberLog into the TeamCity web interface as an administrator and navigate to the Administration > Server Administration page. The version is displayed at the top of the page under the server name.Affected if The displayed version is any build number before 2025.07 (for example, 2024.1, 2024.2, 2025.04, etc.)
-
Verify version from command line or logsIf you cannot access the web UI, check the version from the TeamCity logs directory in a file named teamcity-version.txt or by running: cd <TeamCity home>/bin && ./maintainDB.sh version -T <database> (depending on your installation).Affected if The version returned is before build 2025.07.
-
Confirm password reset functionality is in usePassword reset tokens are generated when users use the 'Forgot Password' feature. This is enabled by default in TeamCity unless explicitly disabled in Administration > Authentication > Password Reset.Affected if Password reset is enabled and your version is before 2025.07, meaning weak hashing applies to your reset tokens.
You are affected if your TeamCity server is running any version prior to 2025.07, as weak cryptographic hashing was applied to password reset and email verification tokens in those releases.
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.07
Upgrade to TeamCity version 2025.07 or later which implements stronger hashing algorithms for authentication tokens.
TeamCity 2025.07 or later
- 1. Back up the TeamCity database and configuration directory before upgrading
- 2. Download TeamCity version 2025.07 or later from the official JetBrains website
- 3. Stop the running TeamCity server
- 4. Install the new TeamCity version following standard upgrade procedures
- 5. Start the TeamCity server
- 6. Verify that password reset and email verification tokens are now using stronger hashing algorithms
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54535 — 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-54535 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