CVE-2025-54531
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 path traversal was possible via plugin unpacking 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 · high confidenceA path traversal vulnerability in JetBrains TeamCity's plugin unpacking mechanism allows attackers to write files to arbitrary locations on Windows systems when malicious plugins are installed, potentially leading to remote code execution.
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
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
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.
-
Identify TeamCity versionAccess the TeamCity web UI and check the version under 'Administration' > 'Server Administration' > 'Server Information', or check the buildServer.properties file in the TeamCity data directory for the version numberAffected if The installed version is any version prior to 2025.07 (for example, 2024.x, 2023.x, or earlier releases)
-
Confirm operating systemVerify the operating system hosting the TeamCity server is Windows. This can be done via systeminfo command or checking the server properties in the TeamCity administrative consoleAffected if The TeamCity server is running on Windows (the vulnerability only affects Windows systems)
-
Review installed pluginsNavigate to 'Administration' > 'Plugins' in the TeamCity web UI and list all installed plugins. Examine each plugin's origin and verify they were obtained from trusted sourcesAffected if Any plugin from an untrusted or unknown third-party source is installed, as the vulnerability is exploited through malicious plugin installation
You are affected if your TeamCity server runs on Windows with a version earlier than 2025.07 and has third-party or untrusted plugins installed.
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 TeamCity to version 2025.07 or later to obtain the patched version, or apply vendor-supplied security updates.
TeamCity 2025.07 or later
- Download TeamCity 2025.07 or later from the official JetBrains website
- Plan and schedule a maintenance window for the upgrade
- Back up your current TeamCity installation including the Data Directory and database
- Stop the TeamCity server service
- Install TeamCity 2025.07 or newer
- Start the TeamCity server service
- Verify the upgrade was successful by logging into the web interface
- Confirm the path traversal vulnerability is resolved by testing plugin installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54531 — 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-54531 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