dbcve.org
TeamcityApplication · Jetbrains

CVE-2026-49374

HIGH · 7.6 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to 2026.1 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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 2026.1 improper permission checks exposed build configuration parameters

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 before version 2026.1, improper permission checks in the build configuration system allowed unauthorized users to access sensitive build configuration parameters that should have been restricted based on user roles and project permissions.

MitigationUpgrade TeamCity to version 2026.1 or later to receive the patched permission validation logic. Review existing user role assignments and build configuration access controls after upgrading.

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

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. Identify TeamCity version
    Access the TeamCity administration dashboard and navigate to 'Administration > Server Administration' or check the login page footer which displays the version number. Alternatively, the version is stored in the <TeamCity home>/buildAgent/distributed-builds.properties or can be queried via the REST API endpoint /app/rest/server/version
    Affected if The installed version is any release prior to 2026.1 (for example, 2025.x, 2024.x, etc.)
  2. Audit build configurations for sensitive parameters
    Navigate to 'Administration > Build Configurations' and review each project's build steps. Focus on parameters defined under 'Parameters' tab in build configurations, especially those marked as password, secret, or containing API keys, tokens, or credentials in their names or values
    Affected if Build configurations exist that contain sensitive parameters (passwords, API keys, tokens, secrets) that should not be visible to all users
  3. Review user role permissions
    Go to 'Administration > User Management > Roles' and examine the roles assigned to non-administrator users. Check which roles have 'View build configuration parameters' or similar read permissions granted
    Affected if Non-admin users or roles have permissions that allow viewing build configuration parameters they should not access based on the principle of least privilege
  4. Check build configuration access control settings
    Inspect individual build configurations by selecting a project, clicking 'Edit', then navigating to 'Access' or 'Permissions' settings. Verify which user groups are granted visibility to sensitive parameters versus which groups actually need access
    Affected if Users outside the intended security group can view or are granted visibility to build configuration parameters through the access control settings

You are affected if your TeamCity version is earlier than 2026.1 AND you have build configurations with sensitive parameters accessible to users who should not have such visibility.

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

Upgrade TeamCity to version 2026.1 or later to receive the patched permission validation logic. Review existing user role assignments and build configuration access controls after upgrading.

Recommended fix High confidence

TeamCity 2026.1

  1. 1. Back up your existing TeamCity data directory and database
  2. 2. Download TeamCity 2026.1 from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the running TeamCity server
  4. 4. Install or extract TeamCity 2026.1 to your server
  5. 5. Start the upgraded TeamCity server
  6. 6. Verify the build configuration parameters are no longer exposed to unauthorized users by testing with a non-privileged account
Caveat Review TeamCity 2026.1 release notes for any breaking changes before upgrading

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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