A vulnerability in JetBrains TeamCity versions prior to 2026.2.1 allowed unauthorized users with limited privileges to read version control system (VCS) file contents and patches of other projects. This issue is due to missing authorization checks.
JetBrains TeamCity versions prior to 2026.2.1 contain an improper authorization vulnerability that allows users to access AWS connections configured for other projects within cloud profiles.
A vulnerability in JetBrains TeamCity versions before 2026.2.1 allowed users with project settings viewer permissions to recover protected credentials via the build parameter editor. This issue could lead to unauthorized disclosure of sensitive information.
A remote code execution vulnerability exists in JetBrains TeamCity versions before 2026.2.1 and 2026.1.5. This flaw is related to personal builds with versioned settings, allowing an attacker with limited privileges to execute code remotely. The vulnerability has a high severity rating with a CVSS score of 7.5.
A remote code execution vulnerability exists in JetBrains TeamCity versions before 2026.2.1 and 2026.1.5. The flaw is related to the handling of Mercurial subrepository paths, which could be exploited to execute arbitrary code remotely.
A vulnerability in JetBrains TeamCity versions prior to 2026.1.5 allows bypassing the untrusted build approval mechanism for GitHub fork pull requests. This could enable unauthorized code execution or compromise the integrity of the build process.
JetBrains TeamCity versions before 2026.2.1 contain a vulnerability where missing validation of Git submodule URLs allows an attacker with limited privileges to read local repositories on the server. This issue is identified as CVE-2026-106219 and has a medium severity with a CVSS score of 6.5. The vulnerability does not impact integrity or availability but allows unauthorized disclosure of local repository contents.