dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-68267

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-16
Fix available
A fix is available. Upgrade to 2025.11.1 or later.
See remediation →
74/100
Remediation priority · Elevated
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 2025.11.1 excessive privileges were possible due to storing GitHub personal access token instead of an installation token

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 confidence

In JetBrains TeamCity before version 2025.11.1, the GitHub integration stored and used personal access tokens (PATs) instead of the more restrictive GitHub App installation tokens, granting the integration excessive permissions beyond what was intended for the build process.

MitigationUpgrade TeamCity to version 2025.11.1 or later, and reconfigure GitHub integrations to use installation tokens with minimal required permissions instead of personal access tokens.

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:< 2025.11.1

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Verify TeamCity server version
    Access the TeamCity administration dashboard and navigate to 'Administration' > 'Server Administration' > 'Server Information' to view the currently installed version number. Alternatively, check the buildServer.properties file or the startup logs for the version identifier.
    Affected if The installed version is any release before 2025.11.1 (e.g., 2025.10.x, 2024.x, or earlier)
  2. Identify GitHub integration configuration
    In the TeamCity administration panel, go to 'Project Settings' > 'GitHub' or 'Integrations' > 'GitHub' to locate any configured GitHub connections. Review the list of projects and build configurations using GitHub as a VCS root.
    Affected if Any GitHub integration is configured or enabled in TeamCity
  3. Examine token type used for GitHub connections
    In the GitHub integration settings for each connection, inspect the authentication configuration. Look for fields labeled 'Access Token', 'Personal Access Token', or similar. Check whether the token is a GitHub personal access token (PAT) or a GitHub App installation token.
    Affected if The authentication is configured using a personal access token (PAT) rather than a GitHub App installation token
  4. Review token permissions scope
    If a PAT is in use, examine the token's granted scopes by reviewing the token configuration in TeamCity or by checking the token's capabilities in GitHub under Settings > Developer settings > Personal access tokens.
    Affected if The PAT grants broad or excessive permissions beyond what is minimally required for build operations (e.g., full repo access, admin rights, or write access to repositories not needed for builds)

A user is affected if their TeamCity installation version is below 2025.11.1 AND they have GitHub integration configured using personal access tokens instead of more restrictive GitHub App installation tokens.

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

Upgrade TeamCity to version 2025.11.1 or later, and reconfigure GitHub integrations to use installation tokens with minimal required permissions instead of personal access tokens.

Recommended fix High confidence

TeamCity 2025.11.1

  1. Review the TeamCity upgrade documentation at www.jetbrains.com before beginning the upgrade process
  2. Ensure you have a complete backup of your TeamCity data directory, database, and configuration files
  3. Download TeamCity 2025.11.1 or later from the official JetBrains website
  4. Stop the running TeamCity server before applying the upgrade
  5. Install the new version following the standard TeamCity upgrade procedure
  6. After upgrading, verify that GitHub integrations are working correctly
  7. Confirm the GitHub personal access token has been replaced with the proper installation token in GitHub App settings if applicable
  8. Start the TeamCity server and verify all services are running normally

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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