CVE-2025-67742
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.11 path traversal was possible via file upload
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 confidenceA path traversal vulnerability in JetBrains TeamCity's file upload functionality allowed attackers to write files to arbitrary locations on the server by manipulating file paths in upload requests. This could lead to remote code execution or service disruption.
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.11CVSS 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.
-
Check TeamCity server version via web UILog into the TeamCity web interface as an administrator. Navigate to 'Administration' > 'Server Administration' > 'Server Information' or click 'Help' > 'About' to view the installed version number.Affected if The displayed version is earlier than 2025.11 (for example, 2025.10, 2025.1, 2024.x, etc.)
-
Check TeamCity version via REST APIMake an authenticated GET request to the TeamCity REST API endpoint: /app/rest/server/version (for example, curl -u admin:password http://teamcity-server:8111/app/rest/server/version)Affected if The returned version string indicates a version lower than 2025.11
-
Check TeamCity version via version.properties fileLocate the TeamCity data directory (typically <TeamCity home>/conf or a separate data directory). Open the 'version.properties' file and read the 'engine.build.number' or 'product.version' property.Affected if The version property value is less than 2025.11
If the installed TeamCity version is any release before 2025.11, the environment is affected by this path traversal vulnerability in the file upload functionality.
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.11
Upgrade to TeamCity version 2025.11 or later to obtain the patch for this vulnerability.
TeamCity 2025.11
- Create a complete backup of your TeamCity database, configuration files, and data directory before proceeding with the upgrade
- Download TeamCity version 2025.11 or later from the official JetBrains website (www.jetbrains.com)
- Stop the running TeamCity server
- Follow the official TeamCity upgrade documentation to install version 2025.11
- Start the upgraded TeamCity server
- Verify the installation by checking that TeamCity is operational and the version displays as 2025.11 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67742 — 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-67742 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