CVE-2026-59793
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 2026.1.2 arbitrary file access was possible via the Perforce VCS integration
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 confidenceIn JetBrains TeamCity versions prior to 2026.1.2, the Perforce VCS (Version Control System) integration contained a path traversal or insecure file handling vulnerability that allowed authenticated users to access arbitrary files on the server file system beyond the intended repository boundaries.
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< 2026.1.2CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed TeamCity versionNavigate to Administration > Server Administration or check the About page in the TeamCity UI. On Linux, also check /opt/teamcity/version.txt or the TeamCity data directory for version files.Affected if The installed version is any release prior to 2026.1.2 (e.g., 2026.1.1, 2025.x, earlier versions).
-
Identify Perforce VCS integration usageNavigate to Administration > Version Control Settings or check the VCS roots configuration in the TeamCity UI. Look for any VCS roots configured with the Perforce connection type.Affected if At least one Perforce VCS root is configured and enabled in TeamCity.
-
Verify Perforce connection configurationExamine the Perforce VCS root settings to confirm the Perforce server connection details (host, port, depot path) are in use. Check if the connection is marked as active.Affected if A Perforce VCS root is actively connected to a Perforce server.
You are affected if your TeamCity version is earlier than 2026.1.2 AND you have a Perforce VCS integration configured. The vulnerability requires both conditions: an older TeamCity version AND an active Perforce VCS connection.
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 · scoped2026.1.2
Upgrade TeamCity to version 2026.1.2 or later. If upgrading is not immediately feasible, disable or restrict the Perforce VCS integration and review access controls to affected instances.
2026.1.2
- 1. Back up your current TeamCity installation and database before proceeding with the upgrade.
- 2. Download JetBrains TeamCity 2026.1.2 from the official JetBrains website or your existing license portal.
- 3. Follow the official TeamCity upgrade documentation to install version 2026.1.2.
- 4. After upgrade, verify the Perforce VCS integration is functioning correctly and that the arbitrary file access vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59793 — 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-2026-59793 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