VulnerabilityPublished 16 Dec 2025

CVE-2025-68164: JetBrains TeamCity · CWE-203

Affects JetBrains TeamCitySource CVE Database V5

Not known to be exploited · CVSS 2.7 Low.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
JetBrains TeamCity	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-68164, European organizations should implement the following specific measures: 1) Restrict access to TeamCity instances to only trusted, high-privilege users and enforce strict role-based access controls to minimize the number of users who can perform Perforce connection tests. 2) Monitor and audit usage of the Perforce connection test feature to detect unusual or unauthorized port scanning activities. 3) Network segmentation should be employed to limit the exposure of TeamCity servers and connected infrastructure, reducing the usefulness of port enumeration. 4) Employ strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. 5) Stay informed about JetBrains security advisories and apply patches promptly once they become available. 6) Consider disabling or restricting the Perforce connection test feature if it is not essential for operations. 7) Conduct regular security assessments and penetration tests focusing on internal threat vectors and privilege misuse scenarios.

Description

CVE-2025-68164 is a low-severity information disclosure vulnerability in JetBrains TeamCity versions prior to 2025.11. It allows an authenticated user with high privileges to perform port enumeration via the Perforce connection test feature. The vulnerability does not impact integrity or availability and requires no user interaction beyond authentication. There are no known exploits in the wild, and no patches have been published yet. The CVSS score is 2.7, reflecting limited confidentiality impact and the need for privileged access. European organizations using TeamCity, especially those integrating Perforce for version control, should be aware of this issue. Mitigation involves restricting high-privilege access, monitoring usage of the Perforce connection test, and applying patches once available. Countries with significant software development sectors and JetBrains customer bases, such as Germany, France, and the UK, are more likely to be affected.

Impact

For European organizations, the primary impact of CVE-2025-68164 is limited to confidentiality loss through information disclosure. While the vulnerability does not directly compromise system integrity or availability, the ability to enumerate ports can aid attackers in mapping internal network structures and identifying additional attack vectors. Organizations using JetBrains TeamCity integrated with Perforce version control systems are particularly at risk. This could be relevant for software development firms, IT service providers, and enterprises with in-house development teams. The impact is mitigated by the requirement for high privilege authentication, reducing the risk from external attackers but increasing concern about insider threats or compromised credentials. The vulnerability could facilitate more sophisticated attacks if combined with other vulnerabilities or social engineering tactics. Given the widespread use of TeamCity in Europe, especially in countries with strong software industries, the threat warrants attention despite its low severity rating.

Summary

CVE-2025-68164 is an information disclosure vulnerability classified under CWE-203 (Information Exposure Through Discrepancy) found in JetBrains TeamCity, a continuous integration and build management system widely used in software development environments. The vulnerability exists in versions prior to 2025.11 and enables port enumeration via the Perforce connection test feature. Specifically, an authenticated user with high privileges can leverage this feature to probe network ports, potentially revealing information about network configurations or services running on the TeamCity server or connected infrastructure. The vulnerability does not allow modification of data or disruption of service, limiting its impact to confidentiality. The CVSS 3.1 base score is 2.7, indicating low severity, with attack vector being network, low attack complexity, requiring privileges, and no user interaction. No known exploits have been reported in the wild, and no official patches have been released at the time of publication. This vulnerability could be used by insiders or attackers who have already gained elevated access to gather intelligence for further attacks or lateral movement within a network.

CWE-203Observable Discrepancy (opens in a new tab)
Base weakness
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Black Box Reverse Engineering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Dec 2025, 15:58 UTC

WeaknessesCWE-203

Technical details

References

Community reviews

Related threats