dbcve.org
TeamcityApplication · Jetbrains

CVE-2026-44413

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 2025.11.5 or later.
See remediation →
84/100
Remediation priority · High
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 2026.1 2025.11.5 authenticated users could expose server API to unauthorised access

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 (or 2025.11.5), an authorization flaw allows authenticated users to expose the server API to unauthorized access. This enables malicious authenticated users to bypass access controls and make API endpoints reachable by parties without valid credentials, potentially leading to data exposure or further exploitation.

MitigationUpgrade TeamCity to version 2026.1 or 2025.11.5 or later. If immediate upgrade is not possible, review and restrict API access configurations and monitor for unauthorized API usage patterns.

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.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify the installed TeamCity version
    Access the TeamCity administration interface and navigate to 'About' page, or check the buildServer.properties file for the version number, or run: `grep -i version <TeamCity_installation_directory>/buildserver/etc/buildserver.properties`
    Affected if The version is lower than 2025.11.5 (or if the version cannot be determined but is known to be an older release)
  2. Confirm API access is enabled
    Review TeamCity's server configuration files (such as main-config.xml or rest-config.xml in the conf directory) and check for enabled API endpoints or web service configurations
    Affected if API/rest endpoints are exposed and reachable from the network (the vulnerability allows these to be accessed by unauthorized parties when this configuration exists)
  3. Inspect authentication settings for API
    Check the authentication configuration in the TeamCity administration panel under 'Authentication' settings, or examine the security-config.xml file for API-related authentication modules
    Affected if API endpoints are configured to use authentication that can be bypassed or are missing proper authorization controls
  4. Review user/role permissions for API exposure
    Examine user roles and permissions in TeamCity's 'Roles and Permissions' section, specifically looking for any custom roles that grant API access permissions to authenticated users
    Affected if Authenticated users have permissions that could allow them to modify API access settings or create unauthorized API tokens

You are affected if your TeamCity installation version is below 2025.11.5 AND API access is enabled in your environment.

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.5 or later
Fixed in 2025.11.5
Interim mitigation

Upgrade TeamCity to version 2026.1 or 2025.11.5 or later. If immediate upgrade is not possible, review and restrict API access configurations and monitor for unauthorized API usage patterns.

Recommended fix Moderate confidence

2025.11.5 (or 2026.1)

  1. Back up TeamCity database and configuration files before starting the upgrade
  2. Stop the TeamCity server service
  3. Download TeamCity 2025.11.5 (or 2026.1 if available) from the official JetBrains website
  4. Install the new version using the standard TeamCity upgrade procedure (run the installer or extract to the existing directory)
  5. Start the TeamCity server service
  6. Log in to TeamCity and verify the server is operational
  7. Confirm the vulnerability is resolved by checking that API endpoints require proper authentication

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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