Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67740: CWE-863 in JetBrains TeamCity

0
Low
VulnerabilityCVE-2025-67740cvecve-2025-67740cwe-863
Published: Thu Dec 11 2025 (12/11/2025, 15:19:05 UTC)
Source: CVE Database V5
Vendor/Project: JetBrains
Product: TeamCity

Description

In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata

AI-Powered Analysis

AILast updated: 12/11/2025, 15:54:20 UTC

Technical Analysis

CVE-2025-67740 is a vulnerability identified in JetBrains TeamCity, a widely used continuous integration and delivery (CI/CD) platform, affecting versions prior to 2025.11. The issue stems from improper access control (CWE-863), which allows users with high privileges to access metadata associated with GitHub App tokens. These tokens are used to authenticate and authorize interactions between TeamCity and GitHub repositories. While the vulnerability does not expose the token secrets themselves, the metadata could include information such as token scopes, creation dates, or associated repository details, which could be leveraged for reconnaissance or to facilitate further attacks. The CVSS 3.1 base score is 2.7 (low), reflecting that the attack vector is network-based (AV:N), requires low attack complexity (AC:L), but crucially requires privileges (PR:H) and no user interaction (UI:N). The scope remains unchanged (S:U), and the impact is limited to confidentiality (C:L) with no impact on integrity or availability. No known exploits are currently in the wild, and no official patches have been released at the time of publication. The vulnerability is primarily a concern for environments where multiple users have elevated privileges, as it could allow an insider or compromised high-privilege account to gather sensitive token metadata. This information could be used to plan further attacks or lateral movement within the CI/CD infrastructure.

Potential Impact

For European organizations, the impact of CVE-2025-67740 is relatively limited due to the low severity and the requirement for high privileges to exploit the vulnerability. However, organizations relying heavily on JetBrains TeamCity for their software development lifecycle could face risks related to information disclosure. Exposure of GitHub App token metadata might enable attackers or malicious insiders to better understand token usage and scope, potentially aiding in crafting more targeted attacks or privilege escalation attempts. This could indirectly affect the confidentiality of source code repositories or disrupt development workflows if leveraged in a broader attack chain. Given the critical role of CI/CD pipelines in modern software delivery, any compromise or information leakage could have downstream effects on software integrity and release processes. European organizations with stringent data protection regulations, such as GDPR, should consider the implications of any unauthorized data exposure, even if limited to metadata. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed proactively to maintain secure development environments.

Mitigation Recommendations

To mitigate CVE-2025-67740, European organizations should implement the following specific measures: 1) Restrict high-privilege access within TeamCity to only essential personnel, enforcing the principle of least privilege to minimize exposure. 2) Monitor and audit access logs for unusual or unauthorized attempts to access GitHub App token metadata, enabling early detection of potential misuse. 3) Segregate duties within the CI/CD environment to prevent a single user from having excessive control or visibility over sensitive tokens. 4) Apply network segmentation and access controls to limit which users and systems can communicate with TeamCity servers. 5) Stay informed about JetBrains security advisories and promptly apply patches or updates once available. 6) Consider rotating GitHub App tokens periodically and reviewing token scopes to minimize potential damage from any exposure. 7) Implement multi-factor authentication (MFA) for all high-privilege accounts to reduce the risk of credential compromise. These targeted actions go beyond generic advice by focusing on access control hardening, monitoring, and operational security practices specific to the vulnerability context.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
JetBrains
Date Reserved
2025-12-11T14:31:21.170Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693ae5917d4c6f31f7b66ff7

Added to database: 12/11/2025, 3:38:57 PM

Last enriched: 12/11/2025, 3:54:20 PM

Last updated: 12/12/2025, 3:55:48 AM

Views: 13

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats