dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-26492

CRITICAL · 9.1 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 2024.12.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 2024.12.2 improper Kubernetes connection settings could expose sensitive resources

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

In JetBrains TeamCity versions before 2024.12.2, improper Kubernetes connection settings in the CI/CD platform's Kubernetes integration feature could expose sensitive resources. The vulnerability stems from how TeamCity handles authentication or connection parameters when interfacing with Kubernetes clusters, potentially allowing unauthorized access to cluster resources or credential exposure.

MitigationUpgrade TeamCity to version 2024.12.2 or later. Review and validate all Kubernetes connection configurations after upgrading to ensure credentials and sensitive resources are properly secured.

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:< 2024.12.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed TeamCity version
    Access the TeamCity administration interface, typically at /admin/admin.html, or check the TeamCity server logs or installation directory for the version number. Compare your version to 2024.12.2.
    Affected if Your TeamCity version is earlier than 2024.12.2
  2. Verify if Kubernetes cloud integration is configured
    Navigate to the TeamCity administration area and look for Cloud profiles or Kubernetes integration settings under the 'Projects' or 'Build Configurations' section. Check if any Kubernetes cloud profile exists.
    Affected if A Kubernetes cloud profile is defined in TeamCity and the version is below 2024.12.2
  3. Review Kubernetes cluster access permissions
    Check the configured Kubernetes cluster permissions and service account settings associated with the TeamCity integration, looking for overly broad RBAC permissions or exposed secrets.
    Affected if The Kubernetes integration uses a service account with excessive cluster permissions or exposes cluster credentials to unauthorized build configurations

You are affected if your TeamCity version is earlier than 2024.12.2 and you have Kubernetes cloud integration enabled with potentially exposed credentials or overly permissive cluster access settings.

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 2024.12.2 or later
Fixed in 2024.12.2
Interim mitigation

Upgrade TeamCity to version 2024.12.2 or later. Review and validate all Kubernetes connection configurations after upgrading to ensure credentials and sensitive resources are properly secured.

Recommended fix High confidence

TeamCity 2024.12.2

  1. Back up your TeamCity server data including the <TeamCity home> directory and database
  2. Stop the TeamCity server service
  3. Download TeamCity 2024.12.2 from the official JetBrains website (www.jetbrains.com)
  4. Install the upgrade following the standard TeamCity upgrade procedure
  5. Start the TeamCity server service
  6. Log in to TeamCity and navigate to the Kubernetes connection settings under Administration > Kubernetes
  7. Review and reconfigure Kubernetes connection settings to ensure credentials are properly secured
  8. Verify that the Kubernetes integration is functioning correctly with the new configuration
Caveat Review TeamCity 2024.12.2 release notes for any new features or configuration changes that may affect your existing setup

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26492 — 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-2025-26492 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