dbcve.org
TeamcityApplication · Jetbrains

CVE-2026-59796

HIGH · 8.1 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 2026.1.2 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 6 weeks old

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 · unedited
In JetBrains TeamCity before 2026.1.2 pipeline modification was possible due to improper permission checks

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 confidence

This is an authorization bypass vulnerability in JetBrains TeamCity CI/CD platform. Before version 2026.1.2, the application performed improper permission checks when modifying pipelines, allowing authenticated users to modify pipeline configurations without appropriate authorization. This could enable privilege escalation or unauthorized changes to build processes.

MitigationUpgrade TeamCity to version 2026.1.2 or later to obtain the patched version with proper permission validation for pipeline modifications.

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
TeamcityApplication
Affected:< 2026.1.2

CVSS 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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check TeamCity server version
    Navigate to Administration > Server Administration > Server Information (or /admin/serverInfo.html) to view the installed TeamCity version number
    Affected if The displayed version is earlier than 2026.1.2 (for example, 2026.1.1, 2026.0.x, or earlier)
  2. Review user authentication settings
    Go to Administration > Authentication to verify which authentication modules are enabled and whether anonymous or unauthenticated access is permitted
    Affected if Anonymous access is enabled or users without proper authentication can access the web interface
  3. Examine pipeline modification permissions
    Navigate to Administration > Users (or /admin/users.html) and check the roles and permissions assigned to each user, specifically looking for non-admin users who have build configuration or pipeline modification rights
    Affected if Users without administrator roles have been granted permissions to create, modify, or delete build configurations or pipelines
  4. Audit recent pipeline changes
    Access the server audit log (Administration > Audit Log or /admin/audit.html) and review recent modifications to build configurations, pipelines, or project settings within the past weeks
    Affected if There are records of build configuration or pipeline changes made by users who should not have modification permissions, or by unknown accounts

You are affected if your TeamCity version is earlier than 2026.1.2 AND your server is accessible to users who should not have pipeline modification permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.1.2 or later
Fixed in 2026.1.2
Interim mitigation

Upgrade TeamCity to version 2026.1.2 or later to obtain the patched version with proper permission validation for pipeline modifications.

Recommended fix High confidence

TeamCity 2026.1.2

  1. 1. Back up the TeamCity data directory and database before proceeding with any upgrade
  2. 2. Download TeamCity version 2026.1.2 from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the TeamCity server and agent services
  4. 4. Follow the official TeamCity upgrade instructions for your installation method (Windows installer, tar.gz, or Docker)
  5. 5. Install or extract TeamCity 2026.1.2 to your deployment location
  6. 6. Start the TeamCity server and agent services
  7. 7. Verify the upgrade was successful by navigating to the TeamCity web interface and checking the version number under Administration > Global Settings
Caveat Review TeamCity 2026.1 release notes for any configuration or feature changes before upgrading; standard upgrade precautions (backups) recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59796 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59796 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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